Bug 1668514

Summary:	[RHOS 13] Cinder SolidFire driver deletes incorrect volume
Product:	Red Hat OpenStack	Reporter:	Cristian Muresanu <cmuresan>
Component:	openstack-cinder	Assignee:	Brian Rosmaita <brian.rosmaita>
Status:	CLOSED ERRATA	QA Contact:	Tzach Shefi <tshefi>
Severity:	medium	Docs Contact:	Tana <tberry>
Priority:	medium
Version:	13.0 (Queens)	CC:	brian.rosmaita, cmuresan, mgeary, senrique, tenobreg
Target Milestone:	---	Keywords:	OtherQA, Triaged, ZStream
Target Release:	13.0 (Queens)	Flags:	tshefi: automate_bug-
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-cinder-12.0.4-9.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, if you deleted a volume through the SolidFire-API/GUI interface and then with OpenStack Platform Block Storage service (cinder), you could inadvertently delete a different volume. With this update, the driver and backend verify the volume ID to prevent accidental deletion.	Story Points:	---
Clone Of:
Clones:	1669679 (view as bug list)		Environment:
Last Closed:	2019-07-10 13:00:41 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:
Bug Depends On:	1669679
Bug Blocks:

Description Cristian Muresanu 2019-01-22 23:29:18 UTC

Description of problem: RFE

Bug in Cinder SolidFire driver deletes incorrect volume

Upstream Bug: https://bugs.launchpad.net/cinder/+bug/1782373
Code Review (Queens): https://review.openstack.org/#/c/615595/

Version-Release number of selected component (if applicable):
Bug still exists even in version 13.0-65 cinder-volume container.

Corey Wright manually applied the patch inside the cinder-volume container and confirmed that this resolves the issue via repeated (20) runs of the full tempest tests against the patched environment.

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tzach Shefi 2019-01-23 06:20:32 UTC

As mentioned above it's a driver issue, not having access to a SolidFire storage system, 
QE can't test/verify this once a fix lands setting OtherQA. 

We cover volume deletion on other backends, 
however problem being a specific driver related, plus no access to storage
means this isn't relevant for close loop, NAKing automated/QE_coverage.

Comment 9 errata-xmlrpc 2019-07-10 13:00:41 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/RHBA-2019:1732