Re-enable trove in scenario003

https://review.openstack.org/#/c/507087/ is merged so
it should be able to deploy trove with keystone v3.

Depends-On: I8d0e200958c813101d72e180c6da8343b5fcae6e
Change-Id: I392cd236196d8ad921f0044f088ecd025116ece2
This commit is contained in:
Alfredo Moralejo 2017-10-16 18:53:00 +02:00
parent aab334bd15
commit 357a20170d

View File

@ -30,10 +30,7 @@ case $::osfamily {
# NOTE(mnaser): We need to figure out why Murano won't accept credentials # NOTE(mnaser): We need to figure out why Murano won't accept credentials
# and how to get it to work with Keystone V3. # and how to get it to work with Keystone V3.
$murano_enabled = false $murano_enabled = false
# TODO (amoralej): trove doesn't work fine with keystone V3. Until it's $trove_enabled = true
# fixed in https://review.openstack.org/#/c/507087/, let's disable it
# so that it doesn't block promotion.
$trove_enabled = false
} }
default: { default: {
fail("Unsupported osfamily (${::osfamily})") fail("Unsupported osfamily (${::osfamily})")