storwize clone volume not in expected iogrop
Bug #1696857 reported by
Gerald McBrearty
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
New
|
Undecided
|
IBM Storage | ||
Bug Description
When I create a cloned volume in Ocata on SVC my volume ends up on the iogrp specified by the iogrp property in the storage type extra spec but in Pike it appears to end up in the same iogrp as the source volume ignoring the storage type.
| Changed in cinder: | |
| assignee: | nobody → IBM Storage (ibm-storage) |
Revision history for this message
| yixuan zhang (yixuan-z) wrote | #1 |
To post a comment you must log in.
Duplicate with https:/