Storwize: Fix the issue while fetching mirror volume relationship info

[Venkata krishna Thumu]

Some cinder operations such as volume create, retype and clone for a volume with replication enabled are failing while updating replication properties of that volume by fetching relationship details. Updated IBM Storwize driver to handle the exception and update cinder DATABASE with the proper data.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit eaafd81e9a121830ce430123a1651b33e7cfff41
Author: venkatakrishnathumu <email address hidden>
Date: Tue Apr 27 11:34:16 2021 +0000

    [SVF] Fix issue to get volume relationship details

    [Spectrum Virtualize Family] Fix the issue while fetching
    relationship details of a volume with replication enabled.

    During some bulk cinder operations such as volume create,
    retype and clone for a volume with replication enabled,
    replication properties to metadata are not being updated
    properly due to an error response from the storage backend
    while trying to fetch volume-relationship details. Users will
    feel that the operation is successful but have no idea that
    volume metadata is partially updated or not updated correctly.
    So, given a fix by applying a retry mechanism to get
    volume-relationship details and raising an exception if that
    backend call still gives an error response.

    Closes-Bug: #1926286

    Change-Id: Iaa03e417727e97011e421e1f45ac2ac5b8e6af6a

[OpenStack Infra (hudson-openstack)]

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