nova-status upgrade check should be run after DB sync and online migrations

Bug #1833064 reported by Mark Goddard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
In Progress
Medium
Mark Goddard
Stein
New
Medium
Unassigned
Train
In Progress
Medium
Mark Goddard
Ussuri
In Progress
Medium
Mark Goddard
Victoria
In Progress
Medium
Mark Goddard

Bug Description

The nova documentation [1] states that the upgrade checks should be run after the DB schema migration and online data migrations have been performed. Currently, kolla ansible executes the upgrade check before starting the upgrade process, which is wrong can could fail.

[1] https://docs.openstack.org/nova/latest/reference/upgrade-checks.html

Mark Goddard (mgoddard)
Changed in kolla-ansible:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)

Fix proposed to branch: master
Review: https://review.opendev.org/665643

Changed in kolla-ansible:
assignee: nobody → Mark Goddard (mgoddard)
status: New → In Progress
Mark Goddard (mgoddard)
Changed in kolla-ansible:
milestone: 11.0.0 → none
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on kolla-ansible (master)

Change abandoned by "Mark Goddard <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/kolla-ansible/+/665643
Reason: Superseded by https://review.opendev.org/c/openstack/kolla-ansible/+/871279

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.