openstack/devstack
Code Issues Proposed changes

Merge "fixed_key: By default use a hardcoded fixed_key across devstack envs"

Browse Source
This commit is contained in:
Zuul 2018-03-09 08:37:35 +00:00 committed by Gerrit Code Review
commit 96c45614c5
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
stack.sh
View File

@ -1259,16 +1259,17 @@ if is_service_enabled g-reg; then
done done
fi fi
# Create a randomized default value for the key manager's fixed_key # NOTE(lyarwood): By default use a single hardcoded fixed_key across devstack
# NOTE(lyarwood): This is currently set to 36 as a workaround to the following # deployments. This ensures the keys match across nova and cinder across all
# libvirt bug that incorrectly pads passphrases that are a multiple of 16 bytes # hosts.
# in length. FIXED_KEY=${FIXED_KEY:-bae3516cc1c0eb18b05440eba8012a4a880a2ee04d584a9c1579445e675b12defdc716ec}
# Unable to use LUKS passphrase that is exactly 16 bytes long
# https://bugzilla.redhat.com/show_bug.cgi?id=1447297
if is_service_enabled nova; then if is_service_enabled nova; then
key=$(generate_hex_string 36) iniset $NOVA_CONF key_manager fixed_key "$FIXED_KEY"
iniset $NOVA_CONF key_manager fixed_key "$key" iniset $NOVA_CPU_CONF key_manager fixed_key "$FIXED_KEY"
iniset $NOVA_CPU_CONF key_manager fixed_key "$key" fi
if is_service_enabled cinder; then
iniset $CINDER_CONF key_manager fixed_key "$FIXED_KEY"
fi fi
# Launch the nova-api and wait for it to answer before continuing # Launch the nova-api and wait for it to answer before continuing