On encrypted volume cloning rekeying doesn't use multipathing

[Gorka Eguileor]

Cloning of encrypted volumes is not using multipathing when attaching the cloned volume to change the encryption key used on the new volume even when it's configured.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit bf23678fe0f8583f80dc216ecbe645debb044220
Author: Gorka Eguileor <email address hidden>
Date: Tue Nov 23 17:27:24 2021 +0100

    Honor multipath config everywhere

    There are multiple places in Cinder where the os-brick call to get the
    connector properties is not passing the "multipath" and
    "enforce_multipath" configuration options.

    This means that some driver won't return a multipathed connection
    information on the initialize_connection RPC call, resulting in a single
    pathed attachment even when the os-brick connector is instantiated with
    the right configuration option.

    This patch fixes the different calls where this is an issue:

    - Backup create
    - Backup restore
    - Kaminario create volume from snapshot
    - Kaminario create volume from volume
    - Volume rekeying

    And also in places where this is not affecting operations because
    drivers are always returning multipathed information:

    - Unity driver
    - IBM FlashSystem

    Closes-Bug: #1951982
    Closes-Bug: #1951977
    Closes-Bug: #1951981
    Change-Id: I73ab87b5aaa4835a814389bc1cdd8016d75f52ef

[OpenStack Infra (hudson-openstack)]

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