VMware driver: unused cached images never clear from datastore's cache folder (usually named vmware_base)
Bug #1212790 reported by
dan wendlandt
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Gary Kotton |
Bug Description
customer reports that that even when they no longer have a VM in their vCenter inventory using a particular image, they are unable to delete the vmdk corrsponding to that image in the vmware_base directory.
Note, the true problem here is that if one cycles through a lot of different images in your deployment, these images are not cleared from the datastore "cache" in any automatic fashion. This issue was encountered when someone tried to perform this task manually using vCenter client. They got the error: “cannot delete file <filename>”
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
milestone: | none → icehouse-1 |
Changed in nova: | |
milestone: | icehouse-1 → icehouse-2 |
Changed in nova: | |
milestone: | icehouse-2 → icehouse-3 |
Changed in nova: | |
milestone: | icehouse-3 → icehouse-rc1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-rc1 → 2014.1 |
To post a comment you must log in.
I've seen this behavior.
The manual work-around is to use one of the vSphere tools (CLI, vSphere Client, NGC) to manually delete the extra images in the cache. This is not a good long-term solution and causes problems with linked_clone based images should an administrator delete the wrong file from cache.
* be careful in the fix not to remove the wrong item from cache
* be mindful of linked_clone based instances which will be partially linked to the file in cache (these instances will crash if a cache file is deleted).