Bug 1554017

Summary:	[RFE][Cinder] Backup restore cancellation support
Product:	Red Hat OpenStack	Reporter:	Christian Schwede (cschwede) <cschwede>
Component:	openstack-cinder	Assignee:	Gorka Eguileor <geguileo>
Status:	CLOSED ERRATA	QA Contact:	Avi Avraham <aavraham>
Severity:	medium	Docs Contact:	RHOS Documentation Team <rhos-docs>
Priority:	medium
Version:	14.0 (Rocky)	CC:	eharney, geguileo, scohen, srevivo, tshefi
Target Milestone:	Upstream M1	Keywords:	FutureFeature, Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-cinder-13.0.0-0.20180710093321.64bebcd.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:49:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christian Schwede (cschwede) 2018-03-10 18:57:43 UTC

Backups can be cancelled by force deleting the in-progress backup, but there is no mechanism to delete the restoring backups. We will now monitor the status of the backup and on any status change will abort the restoration and change the volume status to error.

Comment 5 Tzach Shefi 2018-07-26 14:24:37 UTC

I should technical have a build with needed fixed-in else wouldn't reach ON_QA
Yet the last version I managed to deploy remains insufficient to verify. 
 
openstack-cinder-13.0.0-0.20180703145806.4bc1e5f.el7ost.noarch

Waiting for a newer puddle.

Comment 9 Avi Avraham 2018-10-25 09:06:16 UTC

This RFE was verified 
RPM package version :
puppet-cinder-13.3.1-0.20181013114719.25b1ba3.el7ost.noarch
openstack-cinder-13.0.1-0.20181013185427.31ff628.el7ost.noarch
python2-cinderclient-4.0.1-0.20180809133302.460229c.el7ost.noarch
python-cinder-13.0.1-0.20181013185427.31ff628.el7ost.noarch

according to test run

Comment 12 errata-xmlrpc 2019-01-11 11:49: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.

https://access.redhat.com/errata/RHEA-2019:0045