In-progress migrations may not have stashed instance types
Bug #1164110 reported by
Brian Elliott
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Brian Elliott | ||
Grizzly |
Fix Released
|
High
|
Vish Ishaya |
Bug Description
Instance type information is now stashed in system metadata. However, for existing instances that already have a migration in progress, upgrading a compute node to recent code will cause the following error on startup.
http://
The error causes the compute node to fail to start.
Changed in nova: | |
assignee: | nobody → Brian Elliott (belliott) |
Changed in nova: | |
importance: | Undecided → High |
tags: | added: grizzly-backport-potential |
tags: | removed: grizzly-backport-potential |
Changed in nova: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/26033
Review: https:/