Volume cannot be created in VNX Storage Pool with disks missing
Bug #1436241 reported by
Jeegn Chen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Peter Wang |
Bug Description
When limited disks are missing and Storage Pool is not Offline, the VNX LUN created on that Storage Pool won't be in Ready State but the LUN is still OK for IO access.
Current implementation of create_volume in VNX Cinder Driver will wait until the VNX LUN gets into Ready State or timeout.
Thus the new volume in the back end corresponding to the pool will stuck at "creating" state for a long time before the disks are replaced. This reduces the high availability of the back end.
The logic should be adjusted so that the new volume can get into "available" state as long as the corresponding VNX LUN can serve IO.
tags: | added: drivers emc vnx |
Changed in cinder: | |
assignee: | nobody → Peter Wang (peter.wang) |
Changed in cinder: | |
assignee: | Peter Wang (peter.wang) → Jeegn Chen (jeegn-chen) |
Changed in cinder: | |
assignee: | Jeegn Chen (jeegn-chen) → Peter Wang (peter.wang) |
Changed in cinder: | |
milestone: | none → kilo-rc1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-rc1 → 2015.1.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/167573
Review: https:/