e73f828057
We can't easily add a blocker db sync migration to make sure the migrate_instances_add_request_spec online data migration has been run since we have to iterate both cells (for instances) and the API DB (for request specs) and that's not something we should do during a db sync call. But we want to eventually drop the online data migration and the accompanying compat code found in the api and conductor services. This adds a nova-status upgrade check for missing request specs and fails if any existing non-deleted instances are found which don't have a matching request spec. Related to blueprint request-spec-use-by-compute Change-Id: I1fb63765f0b0e8f35d6a66dccf9d12cc20e9c661
7 lines
248 B
YAML
7 lines
248 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
A new check is added to the ``nova-status upgrade check`` CLI to make sure
|
|
request spec online migrations have been run per-cell. Missing request spec
|
|
compatibility code is planned to be removed in the Stein release.
|