Description of problem: Detaching a volume from a nova instance sometimes not removing it from VNX storage group. It is caused by out-of-date cache for in VNX volume driver. Cache needs to be updated with correct info after creating a storage group. This fix was applied to Ocata and back ported to Newton upstream: https://review.openstack.org/#/c/429439/ This ticket is a request for merge the upstream fix above to Red Hat OSP 10. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Detach a volume from nova instance 2.Use nova and cinder command to confirm the volume is detached. 3.Use NaviSecCli to confirm the LUN is removed from the corresponding storage group. Actual results: The LUN is still in the Storage Group after detaching. Expected results: The LUN is removed from the Storage Group after detaching. Additional info:
Hi, Will there be a patch or minor release for OSP10 that contains this fix? Or do we have to ask customer to upgrade openstack-cinder to 9.1.3-1.el7ost? Thanks.
(In reply to Yue Zhao from comment #1) > Hi, > > Will there be a patch or minor release for OSP10 that contains this fix? Or > do we have to ask customer to upgrade openstack-cinder to 9.1.3-1.el7ost? > > Thanks. It will be shipped as a regular update for OSP10.
When will be the next regular update GA?
Hi Andre, Added OtherQA as I don't have a VNX system to verify this bug. Was asked to set needinfo on you for further verification tracking.
Not sure if it aligns to RedHat's process, but I don't think you need to verify this bug on VNX system. The fix was already verified before it merged into Cinder upstream. The purpose of the ticket is to confirm the upstream fix is pulled into RedHat distro. Since it's in 9.1.3-1.el7ost, I'm ok to close this ticket. Please correct me if I'm wrong. Thanks.
Thanks Yue, Based on your comment above, plus checking that patch has landed on my current build openstack-cinder-9.1.4-3.el7ost.noarch,I've verified this bug.
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-2017:1591