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
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.
Changed in cinder: | |
assignee: | nobody → Kumar Prashant (prashk) |
Changed in cinder: | |
assignee: | Kumar Prashant (prashk) → Helen Walsh (walshh2) |
Changed in cinder: | |
assignee: | Helen Walsh (walshh2) → Kumar Prashant (prashk) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/603294
Review: https:/