Retrieving instance XML in libvirt driver is inconsistent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Rafi Khardalian |
Bug Description
There are many libvirt operations which require the instance XML to function. We use a combination of the existing defined XML, the XML in the instances directory or to_xml function. There's no reason to ever use the the XML files stored in the instances directory; it is there for operational purposes only. Unless we absolutely need the running XML, we should use to_xml to generate the configuration based on what Nova absolutely knows about the instance. Also, we should make sure that if we're keeping an XML file around in the instances directory for operations, that it's always kept up to date.
This will undo any one-off/by-hand changes in favor of absolute consistency with the database, which is preferred. For example, if a running VM references a block device which Nova does not know about, today we'll fail to start that VM based on the fact that none of the logic to re-create iSCSI connections (or otherwise) are executed.
Changed in nova: | |
assignee: | nobody → Rafi Khardalian (rkhardalian) |
status: | New → In Progress |
Changed in nova: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
Fix proposed to branch: master /review. openstack. org/16600
Review: https:/