Nova cell registration logic broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Medium
|
Doug Szumski | ||
Rocky |
Fix Committed
|
Medium
|
Mark Goddard | ||
Stein |
Fix Committed
|
Medium
|
Mark Goddard | ||
Train |
Fix Released
|
Medium
|
Doug Szumski |
Bug Description
The output from `nova-manage cell_v2 list_cells --verbose` contains an extra column which appears not to have existed previously, stating whether the cell is enabled or not. This means that the regex never matches, so existing_cells is always empty.
This impacts the following tasks during cell creation:
- Create base cell for legacy instances (will always run, previously would only run if base cell didn't exist)
- Update base cell for legacy instances (will never run)
- Print warning if a duplicate cell is detected (will never run)
The main user facing impact is likely to be that if they change the rabbit or mysql connection strings, for example by rotating the passwords, they won't get updated for the base cell.
Changed in kolla-ansible: | |
assignee: | nobody → Doug Szumski (dszumski) |
Changed in kolla-ansible: | |
status: | New → In Progress |
description: | updated |
Changed in kolla-ansible: | |
importance: | Undecided → Medium |
The create cell task doesn't fail on multiple invocations, because the `Create base cell for legacy instances` task has ` '"already exists" not in nova_cell.stdout'` in the failed_when conditions. The output when re-registering the base cell is for example: 841d-40a1- b91d-7568d74405 16.`
`The specified transport_url and/or database_connection combination already exists for another cell with uuid f6725b18-