From 31c7d5c796fac2d3d67e893388166f7cf26c6a33 Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Mon, 23 Jul 2018 09:25:08 -0400 Subject: [PATCH] cinder: configure backup_swift_url in subnodes The tempest-multinode-full job is running the c-bak service on the subnode where swift isn't running, and because of the "is_enabled_service swift" check, cinder on the subnode wasn't getting configured to talk to swift so the c-bak service was down. Since chances are good that we're running swift, just configure cinder to always use it. Change-Id: I86b090967dadeeefc017ff0311beeea9441b6ba6 Closes-Bug: #1783128 --- lib/cinder | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/lib/cinder b/lib/cinder index 92d0295b5b..664f423c73 100644 --- a/lib/cinder +++ b/lib/cinder @@ -268,7 +268,12 @@ function configure_cinder { configure_cinder_image_volume_cache fi - if is_service_enabled swift; then + if is_service_enabled c-bak; then + # NOTE(mriedem): The default backup driver uses swift and if we're + # on a subnode we might not know if swift is enabled, but chances are + # good that it is on the controller so configure the backup service + # to use it. If we want to configure the backup service to use + # a non-swift driver, we'll likely need environment variables. iniset $CINDER_CONF DEFAULT backup_swift_url "$SWIFT_SERVICE_PROTOCOL://$SERVICE_HOST:$SWIFT_DEFAULT_BIND_PORT/v1/AUTH_" fi