ScaleIO: Volume name not set correctly in ScaleIO after re-typing of attached volume
Bug #1709705 reported by
Martin Chlumsky
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Confirmed
|
Undecided
|
tssgery |
Bug Description
Some background info: we map volume types to ScaleIO clusters so when we re-type a volume it leads to the volume being migrated between different SIO clusters.
When we re-type an attached volume, the name of the volume in SIO does not get set correctly.
The name of volume that does get set is the encoded uuid of the intermediate volume that becomes the final volume.
I think I narrowed it down to this line:
https:/
It seems only 'available' volumes get the name set correctly.
Changed in cinder: | |
assignee: | nobody → tssgery (eric-aceshome) |
summary: |
- Volume name not set correctly in ScaleIO after re-typing of attached - volume + ScaleIO: Volume name not set correctly in ScaleIO after re-typing of + attached volume |
Changed in cinder: | |
status: | New → Confirmed |
To post a comment you must log in.
I will need to investigate any side effects with renaming the original volume which is attached/in-use