Always create signing_dir regardless of token format
Fixes bug 1088801
devstack does not create signing_dir when keystone token format is UUID.
If the default value of signing_dir is read-only, OpenStack services
such as Quantum server failed to start due to permission denied.
On the keystone client cannot know which token_format is used in keystone
in advance, so signing_dir should be created regardless of the token format.
Change-Id: I1b0d25c1ac4d22d9fb2c5443d15b96fdaa5a4c81
diff --git a/lib/quantum b/lib/quantum
index cb68339..f7fe90a 100644
--- a/lib/quantum
+++ b/lib/quantum
@@ -68,12 +68,10 @@
iniset $conf_file $section admin_tenant_name $SERVICE_TENANT_NAME
iniset $conf_file $section admin_user $Q_ADMIN_USERNAME
iniset $conf_file $section admin_password $SERVICE_PASSWORD
- if [[ "$KEYSTONE_TOKEN_FORMAT" == "PKI" ]]; then
- iniset $conf_file $section signing_dir $QUANTUM_AUTH_CACHE_DIR
- # Create cache dir
- sudo mkdir -p $QUANTUM_AUTH_CACHE_DIR
- sudo chown `whoami` $QUANTUM_AUTH_CACHE_DIR
- fi
+ iniset $conf_file $section signing_dir $QUANTUM_AUTH_CACHE_DIR
+ # Create cache dir
+ sudo mkdir -p $QUANTUM_AUTH_CACHE_DIR
+ sudo chown `whoami` $QUANTUM_AUTH_CACHE_DIR
}
function quantum_setup_ovs_bridge() {