Bug 881737 - nova may delete corrupt VM images with shared VM images
Summary: nova may delete corrupt VM images with shared VM images
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 1.0 (Essex)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.0 Essex
Assignee: Martin Magr
QA Contact: Attila Fazekas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-29 13:38 UTC by Pádraig Brady
Modified: 2016-01-04 14:41 UTC (History)
3 users (show)

Fixed In Version: openstack-nova-2012.2.3-1.el6ost
Doc Type: Bug Fix
Doc Text:
With /var/lib/nova/instances on shared storage the Nova image cache manager may corrupt the checksum files or checksum redundantly or it may incorrectly delete images determining them as unused. This bug is fixed in Nova Folsom release, and in Essex this feature should be disabled by removing parameter remove_unused_base_images = True from nova.conf and adding image_cache_manager_interval = 0 when using shared storage for Nova VM images.
Clone Of:
Environment:
Last Closed: 2013-02-27 12:43:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1075018 0 None None None Never
Launchpad 1078594 0 None None None Never

Description Pádraig Brady 2012-11-29 13:38:52 UTC 
With /var/lib/nova/instances on shared storage...

The VM image cache manager may corrupt the
checksum files or checksum redundantly:
http://pad.lv/1075018

Or it may incorrectly delete images
determining them as unused:
http://pad.lv/1078594

To completely disable this feature, adjust the supplied nova.conf to:
- remove_unused_base_images = True
+ image_cache_manager_interval = 0

The caveat with this is that when not using
shared storage for VM instances, you don't get
the benefit of stale base images being cleaned up.

Folsom has the issue too, but that's being addressed
in a pending stable update, so I'm only logging this
against essex for now.
Comment 2 Nikola Dipanov 2012-12-13 13:26:32 UTC 
So this bug has been fixed in Folsom stable, and we have the config tweak in our essex fedora branch so it's just a matter of making sure we cherry pick this to the RHOS essex branch, as I believe it does not warrant a full backport.
Comment 3 Alan Pevec 2012-12-13 15:03:42 UTC 
Note that pushing an update with changed nova.conf won't fix existing installations where nova.conf was customized b/c it's %config(noreplace)
Comment 4 Martin Magr 2012-12-20 17:15:21 UTC 
Moving to 2.1
Note You need to log in before you can comment on or make changes to this bug.