Bug 1069429 - VMware: delete vm snapshot after nova snapshot
Summary: VMware: delete vm snapshot after nova snapshot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z4
: 4.0
Assignee: Matthew Booth
QA Contact: Jaroslav Henner
URL:
Whiteboard:
Depends On:
Blocks: 1055536
TreeView+ depends on / blocked
 
Reported: 2014-02-25 02:17 UTC by Tracy Jones
Modified: 2022-07-09 06:16 UTC (History)
8 users (show)

Fixed In Version: openstack-nova-2013.2.3-2.el6ost
Doc Type: Bug Fix
Doc Text:
Cause: nova was creating a temporary VMware snapshot during a nova snapshot, but not deleting it on completion. Consequence: VMware guests could end up with a large number of unnecessary snapshots. Fix: The temporary VMware snapshot is now deleted on completion of the nova snapshot operation. Result: VMware guests no longer end up with unnecessary snapshots when taking a nova snapshot.
Clone Of:
Environment:
Last Closed: 2014-05-29 20:35:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 57376 0 None None None Never
Red Hat Product Errata RHSA-2014:0578 0 normal SHIPPED_LIVE Moderate: openstack-nova security, bug fix, and enhancement update 2014-05-30 00:27:05 UTC

Description Tracy Jones 2014-02-25 02:17:21 UTC 
https://review.openstack.org/#/c/57376/
Comment 2 Jaroslav Henner 2014-04-07 10:00:54 UTC 
I presume that when snapshotting, some temporary snapshot is created in the ESXi, which then gets uploaded to glance, so I should check whether it is not left after I do have the complete snapshot in Glance. Right?
Comment 4 Jaroslav Henner 2014-04-17 17:58:52 UTC 
After snapshotting a fresh VM completes, there is no Snapshot file, checking:

/vmfs/volumes/52ced87d-d0fa9d20-ae0d-001b2177e266 # ls 5333299c-bb91-4fd7-b33a-448f401fdad8/
5333299c-bb91-4fd7-b33a-448f401fdad8-b115e487.vswp
5333299c-bb91-4fd7-b33a-448f401fdad8-delta.vmdk
5333299c-bb91-4fd7-b33a-448f401fdad8.nvram
5333299c-bb91-4fd7-b33a-448f401fdad8.vmdk
5333299c-bb91-4fd7-b33a-448f401fdad8.vmsd
5333299c-bb91-4fd7-b33a-448f401fdad8.vmx
5333299c-bb91-4fd7-b33a-448f401fdad8.vmx.lck
5333299c-bb91-4fd7-b33a-448f401fdad8.vmxf
5333299c-bb91-4fd7-b33a-448f401fdad8.vmx~
vmware.log
vmx-5333299c-bb91-4fd7-b33a-448f401fdad8-2971001991-1.vswp

There are no snapshots when using the web client either.
Comment 6 errata-xmlrpc 2014-05-29 20:35:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-0578.html
Note You need to log in before you can comment on or make changes to this bug.