Description of problem: Fix iSCSI multipath rescan issue. Cu. is hitting the issue mentioned in upstream Bug https://review.openstack.org/#/c/433104 Version-Release number of selected component (if applicable): RHEL OSP 10 How reproducible: Checking with Cu. Steps to Reproduce: 1. 2. 3. Actual results: Cinder volume is getting stuck in Detaching state. Here is the multipath output from compute node for stuck cinder volume. ~~~ cat sos_commands/multipath/multipath_-l 3600601609e603d00d80340268cffe611 dm-0 , size=1.0G features='2 queue_if_no_path retain_attached_hw_handler' hwhandler='1 alua' wp=rw `-+- policy='round-robin 0' prio=0 status=enabled `- #:#:#:# - #:# failed undef running ~~~ Expected results: Cinder volume should get detached successfully. Additional info: Nothing atm.
In further testing last week, some key additional fixes were identified for this collection and Gorka is the process of getting those ready to post upstream. We don't have a specific ETA, but we will get the BZs updated once the patches are ready.
Patches are posted for review, comprehensive testing is now passing on iSCSI (FC mpath testing will follow). The relevant patch set will actually be the following set and we will confirm the proper collection needed which may actually vary from the initial set proposed. This BZ will be the right place to track status for the collection. https://review.openstack.org/#/c/455394/ https://review.openstack.org/#/c/455393/ https://review.openstack.org/#/c/455392/
*** Bug 1455738 has been marked as a duplicate of this bug. ***
Verified on openstack-cinder-9.1.4-9.el7ost.noarch On a previous bug tested on same system I had booted 18 instance created vol from image, shutdown=preserve. All 18 instance+volumes were created, later I deleted all 18 instances, which in turn left 18 available volumes. This was repeated four times, total of 72 instances volumes were created detached deleted, no error was hit, no volumes failed to detach. logs on controller and compute don't report use of: iscsiadm --rescan
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:2821