This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
Valid example: CONFIRMED FOR: LIBERTY
** Changed in: nova
Importance: High => Undecided
** Changed in: nova
Status: Confirmed => Expired
** Changed in: nova
Assignee: Chen Fan (fan-chen) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1375868
Title:
libvirt: race between hot unplug and XMLDesc in
_get_instance_disk_info
Status in OpenStack Compute (nova):
Expired
Bug description:
THis came up when analyzing
https://bugs.launchpad.net/nova/+bug/1371677 and there is a lot
information on there. The bug in short is that _get_instance_disk_info
will rely on db information to filter out the volumes from the list of
discs it gets from libvirt XML, but due to the async nature of unplug
- this can still contain a volume that does not exist in the DB and
will not be filtered out, so the code will assume it's an lvm image
and do a blockdev on it which can block for a very long time.
The solution is to NOT use libvirt XML in this particular case (but
anywhere in Nova really) to find out information about running
instances.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1375868/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
