test: follow up on osd_crush_location for containers

This was fixed by 578aa5c2d5 on non-container, we need to apply the same fix for containers. Signed-off-by: Sébastien Han <seb@redhat.com> (cherry picked from commit 77d4023fbe)
2018-08-07 13:38:36 +02:00 · 2018-08-07 13:38:36 +02:00 · b76c7c3afe
parent 9403a3df09
commit b76c7c3afe
2 changed files with 2 additions and 1 deletions
--- a/tests/functional/centos/7/docker/hosts
+++ b/tests/functional/centos/7/docker/hosts
@ -8,6 +8,7 @@ mgr0

 [osds]
 osd0 osd_crush_location="{ 'root': 'HDD', 'rack': 'mon-rackkkk', 'pod': 'monpod', 'host': 'osd0' }"
+osd1 osd_crush_location="{ 'root': 'default', 'host': 'osd1' }"

 [mdss]
 mds0
--- a/tests/functional/centos/7/docker/vagrant_variables.yml
+++ b/tests/functional/centos/7/docker/vagrant_variables.yml
@ -5,7 +5,7 @@ docker: True

 # DEFINE THE NUMBER OF VMS TO RUN
 mon_vms: 3
-osd_vms: 1
+osd_vms: 2
 mds_vms: 1
 rgw_vms: 1
 nfs_vms: 1