PowerMax Driver Train - Safeguarding retype to some in-use replicated modes

Bug #1899137 reported by Helen Walsh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
In Progress
Undecided
Helen Walsh

Bug Description

Host assisted migration is a better option for retyping from a non-replicated
to a replicated (Asynchronous and Metro) modes. So we need to block these
2 retype scenarios when the volume is in-use within the PowerMax driver.

Helen Walsh (walshh2)
Changed in cinder:
assignee: nobody → Helen Walsh (walshh2)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (stable/train)

Fix proposed to branch: stable/train
Review: https://review.opendev.org/757035

Helen Walsh (walshh2)
Changed in cinder:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (stable/train)

Reviewed: https://review.opendev.org/757035
Committed: https://opendev.org/openstack/cinder/commit/fa48c21fba30c6d44ee9b96b8d657575e207e15c
Submitter: Zuul
Branch: stable/train

commit fa48c21fba30c6d44ee9b96b8d657575e207e15c
Author: Helen Walsh <email address hidden>
Date: Fri Feb 7 15:01:48 2020 +0000

    PowerMax Driver - Safeguarding retype to some in-use replicated modes

    Host assisted migration is a better option for retyping from a non-replicated
    to a replicated (Asynchronous and Metro) modes.

    1. Block in-use non-replicated to replicated(Metro and Asynchronous)
    2. Remove any unused code
    3. Differentiate between the production and the management storage groups
    4. Remove rollback code on a cleanup_lun, its not necessary on delete and
        will not always work
    5. Allow for a target device not to exist on the target array
    6. Fix minor issue on metadata on a retype

    Closes-Bug: #1899137
    Change-Id: I6c7c94528ee94183c1df21c25388505b28f1781a
    (cherry picked from commit 92aeec3ad9dbb0482c2531a0b42c06326ae945fd)

tags: added: in-stable-train
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 15.4.1

This issue was fixed in the openstack/cinder 15.4.1 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.