Bug 1668514 - [RHOS 13] Cinder SolidFire driver deletes incorrect volume
Summary: [RHOS 13] Cinder SolidFire driver deletes incorrect volume
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: ---
: 13.0 (Queens)
Assignee: Brian Rosmaita
QA Contact: Tzach Shefi
Tana
URL:
Whiteboard:
Depends On: 1669679
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-22 23:29 UTC by Cristian Muresanu
Modified: 2019-07-10 13:01 UTC (History)
5 users (show)

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.
Clone Of:
: 1669679 (view as bug list)
Environment:
Last Closed: 2019-07-10 13:00:41 UTC
Target Upstream Version:
Embargoed:
tshefi: automate_bug-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1782373 0 None None None 2019-01-23 15:09:40 UTC
OpenStack gerrit 615595 0 None MERGED SF ensure the correct volume is deleted 2020-08-05 21:44:19 UTC
Red Hat Product Errata RHBA-2019:1732 0 None None None 2019-07-10 13:01:06 UTC

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


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