Can't delete instance with numa_topology after upgrading from kilo
Bug #1596119 reported by
Chris Stone
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Hans Lindgren | ||
Mitaka |
Fix Released
|
High
|
Lee Yarwood |
Bug Description
Using the RDO Kilo version of Nova (2015.1.0-3) with dedicated cpu pinning populates the numa_topology database field with data at "nova_object.
Updating from Kilo to Mitaka produces the same problem.
tags: | added: upgrades |
tags: | added: unified-objects |
Changed in nova: | |
status: | New → Incomplete |
tags: | added: liberty-backport-potential mitaka-backport-potential |
Changed in nova: | |
importance: | Undecided → High |
tags: | removed: liberty-backport-potential |
To post a comment you must log in.
Attaching log info from nova compute during an attempted start of a stopped instance