VMAX Driver - A cinder manage operation for a VMAX volume for an invalid reference shouldn't result in any storage operations on the VMAX

Bug #1792889 reported by Kumar Prashant
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
Kumar Prashant

Bug Description

While performing a cinder manage operation using the VMAX driver, the external reference is supposed to be of exactly 5 digits. If the provided external reference is of a different length, then this will lead to the operation to fail eventually but may lead to some storage related operations on the array. This shouldn't happen and the driver should throw an exception without performing any storage operations on the array.

Kumar Prashant (prashk)
Changed in cinder:
assignee: nobody → Kumar Prashant (prashk)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

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

Changed in cinder:
status: New → In Progress
Changed in cinder:
assignee: Kumar Prashant (prashk) → Helen Walsh (walshh2)
Changed in cinder:
assignee: Helen Walsh (walshh2) → Kumar Prashant (prashk)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

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

commit 6fee4e260c2c4e9418bab8c9bf8c19d47840a0e3
Author: Kumar Prashant <email address hidden>
Date: Tue Sep 18 11:59:22 2018 +0530

    VMAX Driver - Fix for invalid device id length

    The external reference supplied while managing an existing device
    should be of exactly 5 digits as device ids on the VMAX array are
    of exactly 5 digits. The VMAX driver should perform a check and throw
    appropriate error.

    Change-Id: I06cc3e107a5b07f8f00e9a9a025a0152199092df
    Closes-bug: 1792889

Changed in cinder:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (stable/rocky)

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/639758

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 14.0.0.0rc1

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (stable/rocky)

Reviewed: https://review.openstack.org/639758
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=d3bc8e5596b51588b509b59eedf0723272f813c4
Submitter: Zuul
Branch: stable/rocky

commit d3bc8e5596b51588b509b59eedf0723272f813c4
Author: Kumar Prashant <email address hidden>
Date: Tue Sep 18 11:59:22 2018 +0530

    VMAX Driver - Fix for invalid device id length

    The external reference supplied while managing an existing device
    should be of exactly 5 digits as device ids on the VMAX array are
    of exactly 5 digits. The VMAX driver should perform a check and throw
    appropriate error.

    Change-Id: I06cc3e107a5b07f8f00e9a9a025a0152199092df
    Closes-bug: 1792889
    (cherry picked from commit 6fee4e260c2c4e9418bab8c9bf8c19d47840a0e3)

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

This issue was fixed in the openstack/cinder 13.0.5 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.