archive_deleted_rows --until-complete stops if api database is not configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Surya Seetharaman | ||
Queens |
Fix Committed
|
Medium
|
Surya Seetharaman |
Bug Description
This change https:/
However, with 'superconductor' mode configurations where the cell shouldn't be configured to reach the API database, this will fail, as seen here:
So in the case that the API database isn't configured in the nova.conf being used to run the CLI, we should gracefully handle the condition and continue archiving.
I think we could either do this by handling the CantStartEngine
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in nova: | |
assignee: | nobody → Surya Seetharaman (tssurya) |
Adapted Solution : Using the CantStartEngine Error for handling this gracefully, continuing the archival and informing the user that 0 instance_mappings and 0 request_specs rows were archived because the CONF.api_ database. connection was not set.