Bug 1684220 - [OSP14] When a a storagegroup is destroyed because it's empty, VNX driver doesn't recreate it upon subsequent attachment
Summary: [OSP14] When a a storagegroup is destroyed because it's empty, VNX driver doe...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
: 14.0 (Rocky)
Assignee: Pablo Caruana
QA Contact: Tzach Shefi
Tana
URL:
Whiteboard:
: 1692232 (view as bug list)
Depends On:
Blocks: 1682647 1693338
TreeView+ depends on / blocked
 
Reported: 2019-02-28 18:25 UTC by David Vallee Delisle
Modified: 2019-04-30 17:47 UTC (History)
7 users (show)

Fixed In Version: openstack-cinder-13.0.3-2.el7ost
Doc Type: Bug Fix
Doc Text:
Prior to this update, when `destroy_empty_storage_group` was enabled and a storage group was destroyed after it was emptied, the VNX driver or storops cache was not updated and the driver did not recreate the storage group upon subsequent attachment. The storage group cache was not updated, causing the subsequent attachment of volumes to the same host to fail. With this update, the storage group is updated with poll after deleting it. The storage group is not deleted from cache explicitly, but the status is set to `not-exist`. As a result, subsequent attaching creates the storage group if the latest status is `not-exist`.
Clone Of: 1682647
: 1693338 (view as bug list)
Environment:
Last Closed: 2019-04-30 17:47:26 UTC
Target Upstream Version:
Embargoed:
tshefi: automate_bug-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1817385 0 None None None 2019-02-28 18:26:46 UTC
OpenStack gerrit 640120 0 None MERGED VNX: update sg in cache 2020-07-31 18:15:05 UTC
Red Hat Product Errata RHBA-2019:0946 0 None None None 2019-04-30 17:47:29 UTC

Comment 2 Alan Bishop 2019-03-25 16:52:03 UTC 
*** Bug 1692232 has been marked as a duplicate of this bug. ***
Comment 7 errata-xmlrpc 2019-04-30 17:47:26 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:0946
Note You need to log in before you can comment on or make changes to this bug.