Upgrade to Ocata: Keystone Intermittent Missing 'options' Key
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
In Progress
|
Medium
|
Unassigned | ||
openstack-ansible |
Fix Released
|
Medium
|
Alex Redinger |
Bug Description
During upgrades of Newton-EOL AIOs to Ocata, Keystone installation fails at the "Ensure service tenant" play of the os-keystone_
This occurs using the provided run-upgrade.sh script.
Keystone logs are thus:
INFO keystone.
DEBUG keystone.
INFO keystone.
ERROR keystone.
ERROR keystone.
ERROR keystone.
ERROR keystone.
ERROR keystone.
ERROR keystone.
ERROR keystone.
ERROR keystone.
ERROR keystone.
It appears that the sql identity backend ensures an 'options' key should exist with .../keystone/
It should be noted that rerunning the install process causes it to be successful.
Changed in openstack-ansible: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Noticing that even on successfull upgrades there are usually a few failed attempts at running the "Ensure service tenant" play. Simply adding more retires should greatly mitigate upgrade failures going forward.