Fix devstack plugin for multinode deployment issues
- Call create_heat_accounts irrespective of whether keystone is enabled or not. - Use hardcoded auth_encryption_key Change-Id: I03fab7f986ec2a9703044f4bff31d477e2e7fe6a
This commit is contained in:
parent
4c9c588185
commit
48622d46f4
@ -140,7 +140,9 @@ function configure_heat {
|
||||
fi
|
||||
|
||||
iniset $HEAT_CONF database connection `database_connection_url heat`
|
||||
iniset $HEAT_CONF DEFAULT auth_encryption_key $(generate_hex_string 16)
|
||||
# we are using a hardcoded auth_encryption_key as it has to be the same for
|
||||
# multinode deployment.
|
||||
iniset $HEAT_CONF DEFAULT auth_encryption_key "767c3ed056cbaa3b9dfedb8c6f825bf0"
|
||||
|
||||
iniset $HEAT_CONF DEFAULT region_name_for_services "$REGION_NAME"
|
||||
|
||||
|
@ -26,10 +26,7 @@ if is_heat_enabled; then
|
||||
cleanup_heat
|
||||
echo_summary "Configuring heat"
|
||||
configure_heat
|
||||
|
||||
if is_service_enabled key; then
|
||||
create_heat_accounts
|
||||
fi
|
||||
create_heat_accounts
|
||||
|
||||
elif [[ "$1" == "stack" && "$2" == "extra" ]]; then
|
||||
# Initialize heat
|
||||
|
Loading…
x
Reference in New Issue
Block a user