nova-manage db migrate_flavor_data doesn't do instances not in instance_extra
Bug #1447132 reported by
Joshua Hesketh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Dan Smith | ||
Kilo |
Fix Released
|
High
|
Unassigned |
Bug Description
nova-manage db migrate_flavor_data selects all of the instances by joining them to the instance_extra table and then checks which ones have flavor information in the metadata table or the extras table. However, if an instance isn't in instance_extra (for example, it hasn't been written to since the creation of the extras table) then it won't be migrated (even if it isn't deleted AND has flavor info in the metadata table).
migrate_flavor_data should select all of the instances in the metadata table with flavor information and migrate those.
tags: | added: db |
Changed in nova: | |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: kilo-backport-potential |
Changed in nova: | |
assignee: | nobody → Dan Smith (danms) |
status: | Triaged → In Progress |
no longer affects: | nova/kilo |
tags: | removed: kilo-rc-potential |
Changed in nova: | |
milestone: | none → liberty-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | liberty-1 → 12.0.0 |
To post a comment you must log in.
Patch is here: https:/ /review. openstack. org/176387