Unrescue causes 'Device in use' when trying to unplug VBD devices
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Dan Prince |
Bug Description
I get the following exceptions when trying to unrescue an instance in which I have mounted the original image:
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: function(self, context, instance_id, *args, **kwargs)
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: self.driver.
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: self._vmops.
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: self._destroy_
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: self._destroy_
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: VMHelper.
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: raise StorageError(
(nova.exception): TRACE: StorageError: Unable to unplug VBD OpaqueRef:
---
There really is no need to attempt to hot unplug VBD devices. We should simply shutdown the rescue instance, wait for shutdown to complete, and then destroy the VDI.
Related branches
- Chris Behrens (community): Needs Information
- Nova Core security contacts: Pending requested
-
Diff: 71 lines (+20/-14)1 file modifiednova/virt/xenapi/vmops.py (+20/-14)
Changed in nova: | |
status: | New → Incomplete |
status: | Incomplete → In Progress |
assignee: | nobody → Dan Prince (dan-prince) |
importance: | Undecided → High |
Changed in nova: | |
milestone: | none → essex-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
Dan. Was this ever addressed?