Bug 1256826 - [RFE] Alter generation of fail-safe snapshot delete so that it is created before snapshot request is presented to provider.
[RFE] Alter generation of fail-safe snapshot delete so that it is created bef...
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis (Show other bugs)
x86_64 Linux
unspecified Severity high
: GA
: cfme-future
Assigned To: John Hardy
Dave Johnson
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2015-08-25 10:18 EDT by Thomas Hennessy
Modified: 2018-01-04 13:26 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-01-04 13:26:26 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Thomas Hennessy 2015-08-25 10:18:04 EDT
Description of problem: BZ 1256821 reports issue where snapshot request to openstack results in a reported connection error, but the snapshot is created, never to be deleted, consuming disk space in provider storage environment.

Version-Release number of selected component (if applicable):

How reproducible: refer to BZ 1256821

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
the fail-safe snapshot delete was introduced into CFME as a means to ensure that regardless of what happened to the vmscan processing, any snapshot file created in the provider environment would be removed after not more than 60 minutes.  The BZ 1256821 demonstrates that generating that snapshot fail-safe request *after* the snapshot create request is not sufficient to achieve the desired results, (ie, do no harm to the provider storage environment).  Createing the failsafe request before requesting the snapshot create will preserve as best we can the attempt to return the storage environment back to the state before the snapshot was created.

Note You need to log in before you can comment on or make changes to this bug.