PowerMax - Group rename error

[Helen Walsh]

Description:
When a Generic Volume Group is renamed in OpenStack any subsequent attempt to find the corresponding storage group on the PowerMax fails. This is because the search criteria is too tight. The GVG name is <user-friendly-name>+<openstack-group-uuid>.

How to reproduce:
1. Create a GVG using PowerMax driver
2. Rename the GVG in OpenStack
3. Attempt to add a volume to the GVG created in step 1.

Error:
Cannot find storage group on PowerMax

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit 1ae4ac4486bf3915e2b619e334dfb479a91bfa54
Author: Helen Walsh <email address hidden>
Date: Mon Jul 19 17:35:53 2021 +0100

    PowerMax Driver - Fix for renaming GVG

    When a Generic Volume Group is renamed in OpenStack, the
    corresponding storage group on the PowerMax does not reflect
    this new name. The name format is <user-supplied-name><uuid>
    on the PowerMax and now the former section has been changed.

    To fix this issue we search based on the uuid alone and not
    the combination of user supplied name and uuid. Once
    the modified storage group object is returned successfully,
    the storage group is renamed on the PowerMax. Any subsequent
    operation on the Generic Volume Group will proceed as before.

    Closes-Bug: #1936848
    Change-Id: Ia49ac163e6d9995368ef7931e51835f753b6623e

[OpenStack Infra (hudson-openstack)]

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