XenAPI doesn't clean up failed build's VHDs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| OpenStack Compute (nova) |
High
|
Rick Harris |
Bug Description
Failed build's VHDs continue to remain on the file system:
[root@xs ~]# ls -l /var/run/
11
[root@xs ~]# xe vm-list
uuid ( RO) : 8aa565eb-
name-label ( RW): Nova
power-state ( RO): running
uuid ( RO) : 7a570ee8-
name-label ( RW): Control domain on host: xs
power-state ( RO): running
uuid ( RO) : 068d3d7d-
name-label ( RW): XenServer DDK
power-state ( RO): halted
Changed in nova: | |
importance: | Undecided → High |
Changed in nova: | |
status: | New → Confirmed |
Rick Harris has made a lot of changes recently to fix problems where VDIs were leaking on failed builds:
https:/
https:/
https:/
I'm going to mark this as Fix Committed for now because of all of the work he has done. If VDIs are still seen leaking, please reopen (or open new bug) with details on the new failure.
Changed in nova: | |
status: | Confirmed → Fix Committed |
Changed in nova: | |
milestone: | none → essex-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
assignee: | nobody → Rick Harris (rconradharris) |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
This could be a regression of bug #694935
However the original bug fix took care only of VDIs created from raw images in Glance/Objectstore.
The code for VHD download was added concurrently with this fix, and therefore currently lacks 'protection' against instance build failure. Therefore, if the bug has been observed while building instance from VHDs that would explain it. Otherwise it's a regression.