Bug 1622535
| Summary: | [OSP-13] NetApp: Ontap FC/iSCSI drivers does not support force_detach | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Erlon <erlon.cruz> |
| Component: | openstack-cinder | Assignee: | Elise Gafford <egafford> |
| Status: | CLOSED ERRATA | QA Contact: | Avi Avraham <aavraham> |
| Severity: | urgent | Docs Contact: | Kim Nylander <knylande> |
| Priority: | urgent | ||
| Version: | 13.0 (Queens) | CC: | abishop, atiwary, egafford, lmarsh, pgrist, srevivo, tshefi |
| Target Milestone: | z3 | Keywords: | OtherQA, Triaged, ZStream |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-cinder-12.0.3-3.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: |
This fix enables the NetApp ONTAP FC/iSCSI drivers to succeed in the force_detach action, which terminates every connection between the specified volume and any host it is mapped to.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-13 22:13:36 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: | |||
| Bug Blocks: | 1622538 | ||
|
Description
Erlon
2018-08-27 12:19:48 UTC
Hi Elise, When will that be on GA? I have updated the package and still not in this version you mentioned: [root@overcloud-cinder-controller-0 heat-admin]# yum install python-cinder Loaded plugins: product-id, search-disabled-repos, subscription-manager Package 1:python-cinder-12.0.3-2.el7ost.noarch already installed and latest version Nothing to do Hi Erlon, For the sake of completeness: as Alan noted in the 12.0 clone of this bug, this fix will be available after QA, in version openstack-cinder-12.0.3-3.el7ost or above. The bug state is the best indicator of progress; at present it is MODIFIED, meaning that the fix has been backported, committed, reviewed, passed dev CI, and pushed into a testable build. From here it will flow into ON_QA, VERIFIED, and RELEASE_PENDING (which are all pretty self-explanatory) on its way to CLOSED, at which point the fix will be generally available. Thanks, Elise Hi Elise, Thanks for the detailed description, it was very helpful. Erlon *** Bug 1638127 has been marked as a duplicate of 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/RHSA-2018:3601 |