[Storwize] mkhost command failure

[Harsh Ailani]

Customer is getting the below error during attach operation in iSCSI:

2022-07-26 08:27:04.554 43 ERROR cinder.volume.drivers.ibm.storwize_svc.storwize_svc_iscsi [req-20f8a885-046e-4f45-a71b-107506ffa1a2 1295c9910e3548e7a6c404d73f449b0d 5ed10252a27d43328c8803616cd809d2 - default default] _get_single_iscsi_data: No node found in I/O group 0 for volume volume-4cd0ae48-30b0-41ed-af9f-646fba247e30.
2022-07-26 08:27:04.554 43 ERROR cinder.volume.drivers.ibm.storwize_svc.storwize_svc_iscsi [req-20f8a885-046e-4f45-a71b-107506ffa1a2 1295c9910e3548e7a6c404d73f449b0d 5ed10252a27d43328c8803616cd809d2 - default default] initialize_connection: Failed to export volume volume-4cd0ae48-30b0-41ed-af9f-646fba247e30 due to Bad or unexpected response from the storage volume backend API: _get_single_iscsi_data: No node found in I/O group 0 for volume volume-4cd0ae48-30b0-41ed-af9f-646fba247e30..: cinder.exception.VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: _get_single_iscsi_data: No node found in I/O group 0 for volume volume-4cd0ae48-30b0-41ed-af9f-646fba247e30.

Even though the customer's environment had the nodes on iogrp0, the driver wasn't able to find that node.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/cinder/+/853126

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/cinder/+/853126
Committed: https://opendev.org/openstack/cinder/commit/54872f9b6caa1a6ffa06d4cc19d07a04a90b26e1
Submitter: "Zuul (22348)"
Branch: master

commit 54872f9b6caa1a6ffa06d4cc19d07a04a90b26e1
Author: haailani <email address hidden>
Date: Wed Aug 17 06:37:12 2022 +0000

    [SVf]: mkhost failure when volume and node are on different iogrp

    Attach operation fails when volume and back-end host are on different
    iogroup. The assignment of the node IP addresses is done outside the
    try block, and the "for ip_data in lsip_resp" loop. Because of this
    the loop was not consistent before, so only latest node was detected
    instead of all nodes.

    Closes-Bug: #1985065
    Change-Id: I72074357140e9817eee704b6e9ebfd7f50343235

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cinder 22.0.0.0rc1 release candidate.