After "nova reboot" the instance looses the nova-volume on its xml
Bug #1012717 reported by
Mercadolibre CloudBuilders
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
Essex |
Fix Released
|
High
|
Rafi Khardalian |
Bug Description
Hi, we are using Essex final release with nova volumes.
On an instance with nova-volumes is rebooted from inside the guest, it comes back with the nova-volume successfull.
But if we issue a "nova reboot [id]" the instance looses the nova volume, and the device block definition dissapears in the /var/run/
We think its a very critical bug.
If you need any kind of extra information please do.
Cheers.
tags: | added: essex-backport |
To post a comment you must log in.
We think the problem is on "_soft_reboot" over /usr/share/ pyshared/ nova/virt/ libvirt/ connection. py.