Bug 1669679 - [RHOS 14] Cinder SolidFire driver deletes incorrect volume
Summary: [RHOS 14] Cinder SolidFire driver deletes incorrect volume
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: ---
: 14.0 (Rocky)
Assignee: Brian Rosmaita
QA Contact: Tzach Shefi
Tana
URL:
Whiteboard:
Depends On:
Blocks: 1668514
TreeView+ depends on / blocked
 
Reported: 2019-01-25 22:58 UTC by Brian Rosmaita
Modified: 2019-07-02 19:44 UTC (History)
2 users (show)

Fixed In Version: openstack-cinder-13.0.3-2.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, if a user deletes a volume through the Solidfire API or GUI interface and then subsequently requests that same volume to be deleted through Cinder, the driver could delete a volume that was not the target for the delete request. This update modifies the Cinder Solidfire driver to validate the volume ID in the delete request to prevent unexpected data loss.
Clone Of: 1668514
Environment:
Last Closed: 2019-07-02 19:43:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1782373 0 None None None 2019-01-25 22:58:57 UTC
OpenStack gerrit 623036 0 None None None 2019-01-25 22:58:57 UTC
Red Hat Product Errata RHBA-2019:1678 0 None None None 2019-07-02 19:44:14 UTC

Description Brian Rosmaita 2019-01-25 22:58:57 UTC 
+++ This bug was initially created as a clone of Bug #1668514 +++

Bug in Cinder SolidFire driver deletes incorrect volume

Upstream Bug: https://bugs.launchpad.net/cinder/+bug/1782373

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
Comment 7 errata-xmlrpc 2019-07-02 19:43:59 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:1678
Note You need to log in before you can comment on or make changes to this bug.