libvirt image cache manager doesn't handle shared storage during cleanup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Michael Still | ||
Folsom |
Fix Released
|
Critical
|
Mark McLoughlin |
Bug Description
On 11/14/2012 04:03 PM, Sam Morrison wrote:
> After the upgrade which went relatively smoothly (a lot easier than
> diablo -> essex) almost all our base images were deleted by the image
> cache clean up.
> I can't explain how this happened. We lost a total of about 70 images
> that affected ~200 running instances.
>
> We have since disabled this flag until we can find out what went wrong.
> I can see it in the logs and if this flag is enabled it would delete a
> lot of in use base files still.
>
> We have an nfs mounted /var/lib/
> dir is located so I'm wondering if this had something to do with it?
> Is the image cache cleanup meant to work in a shared instance storage
> environment?
Changed in nova: | |
milestone: | none → grizzly-1 |
status: | Fix Committed → Fix Released |
tags: | removed: folsom-backport-potential |
Changed in nova: | |
milestone: | grizzly-1 → 2013.1 |
Fix proposed to branch: master /review. openstack. org/16134
Review: https:/