[Bug 1607313] Re: Inconsistency in data stored in libvirt.xml file
1607313 at bugs.launchpad.net
Mon Feb 19 20:06:29 UTC 2018
Author: Danil Akhmetov <dakhmetov at mirantis.com>
Date: Fri Nov 18 19:27:37 2016 +0300
Use proper user and tenant in the owner section of libvirt.xml.
Nova takes instance ownership info from request context when it updates
libvirt.xml, which is not always correct. A real instance owner should
be used to avoid inconsistency in the data stored in the XML file.
(cherry picked from commit 3f2935872da311f79b5fd4d51fb50b4fcf8d2bcd)
** Changed in: cloud-archive/ocata
Status: Confirmed => Fix Committed
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
Inconsistency in data stored in libvirt.xml file
Status in Ubuntu Cloud Archive:
Status in Ubuntu Cloud Archive mitaka series:
Status in Ubuntu Cloud Archive ocata series:
Status in OpenStack Compute (nova):
Status in OpenStack Compute (nova) ocata series:
Status in nova package in Ubuntu:
Status in nova source package in Xenial:
Operations involved :
The above mentioned operations on instances lead to creation of a new
instance on a new compute host. It has been observed that the 'owner'
information in the libvirt.xml file is populated with the
username/projectname(tenantname) of the user performing any of the
There's an instance 'ins-1' in project/tenant 'pro-1' owned by user 'user01' launched on compute host 'compute-101'.
Now, an admin user named 'osadmin' from project 'admin', performs operation
`nova live-migration asdfghi123xyz compute-102`
* AD-123 (ID if ins-1)
This leads to a live migration of ins-1 from compute-101 to compute-102.
Now, the file /var/lib/nova/instances/asdfghi123xyz/libvirt.xml in compute-102 will have
which ideally should be,
This inconsistency is seen in all the operations mentioned, i.e. evacuate, migrate, live-
Related commands :
nova live-migration SERVER HOST_NAME
nova evacuate EVACUATED_SERVER_NAME HOST_B
nova migrate VM_ID
To manage notifications about this bug go to:
More information about the Ubuntu-openstack-bugs