VMAX Driver - A failed manage operation can lead to subsequent manage operations on the same volume to fail

[Kumar Prashant]

A failed manage existing operation using the VMAX driver can cause future manage operations to fail if the failure happened after the volume was renamed on the VMAX array. This is because of rollback to rename the volume back to it's original name

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/603202

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/603202
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b67e2de51521f1836003bdbbad9a5421251e530e
Submitter: Zuul
Branch: master

commit b67e2de51521f1836003bdbbad9a5421251e530e
Author: Kumar Prashant <email address hidden>
Date: Mon Sep 17 23:19:19 2018 +0530

    VMAX Driver - Rollback for manage existing volume

    Implements rollback for manage existing volume for the scenario
    when the manage operation fails after the volume has been already
    renamed on the array

    Change-Id: I40f861819d8ce43a128d411ff58a1a703d8b1e0b
    Closes-bug: 1792884

[OpenStack Infra (hudson-openstack)]

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