Upgrade from Ocata to Pike caused instance listing to fail
Bug #1809260 reported by
Andrea Ieri
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Charms Deployment Guide |
Fix Released
|
High
|
Unassigned | ||
| OpenStack Nova Cloud Controller Charm |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
This really seems awfully similar to LP#1809210 (and it happened in the same site): after the upgrade listing all instances yielded the following failure:
This service is older (v9) than the minimum (v16) version of the rest of the deployment. Unable to continue. (HTTP 400)
Looking at the nova database, indeed there were some stale entries with version=9:
https:/
The juju-machine-
Instance listing resumed working only after all version=9 entries were deleted.
| summary: |
- Upgrade from Newton to Ocata caused instance listing to fail + Upgrade from Ocata to Pike caused instance listing to fail |
Revision history for this message
| James Page (james-page) wrote | #1 |
| Changed in charm-deployment-guide: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in charm-nova-cloud-controller: | |
| status: | New → Triaged |
Revision history for this message
| James Page (james-page) wrote | #2 |
Revision history for this message
| James Page (james-page) wrote | #3 |
| Changed in charm-nova-cloud-controller: | |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to charm-deployment-guide (master) | #4 |
| Changed in charm-deployment-guide: | |
| status: | Triaged → Fix Released |
| tags: | added: openstack-upgrade |
To post a comment you must log in.
@aieri
I'm assuming that the v9 based services and the machines hosting them where around at some point in time; the 'Service' db code checks the version and raises this exception for everything that does not meet the minimum requirement hence why deleting the entries resolved the issue.
I think we at a minimum need to add some pre-flight check notes to the charm deployment guide to purge any down/old service entries from nova prior to upgrades. This can probably be done in advance of an upgrade but obviously can't be done post upgrade as the API will continue to throw these errors.