Storwize volume isn't displayed as attached after successful migrate due to retype
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
High
|
TaoBai |
Bug Description
1. Create type-1 on svc
2. Create type-7 on v7k
3. Create volume da057a4f-
4. Retype the volume from type-1 to type-7
5. There will be two volumes in the cinder list in the retyping process
-------
ID Status Name Size Volume Type Bootable Attached to
-------
00beab97-
da057a4f-
6. Do attach for the volume :
stack@ubuntu131
7. Check the volume status after retype finished, it was found:
da057a4f-
The status for the volume is available, but the attached to is the hostid.
8. Do attach again for the volume, it will be refused:
stack@ubuntu131
ERROR (BadRequest): Invalid volume: already attached (HTTP 400) (Request-ID: req-63c6af29-
Since the attaching was successful, the status of the volume should be in-use after retyping finished.
tags: | added: drivers storwize |
Changed in cinder: | |
importance: | Undecided → High |
Changed in cinder: | |
assignee: | nobody → git-harry (git-harry) |
summary: |
- The volume status is still available when successful attached between - the retyping migrating process + Volume is available when successful attached during retyping migrating |
tags: | added: icehouse-backport-potential |
Changed in cinder: | |
milestone: | juno-1 → juno-2 |
summary: |
- Volume is available when successful attached during retyping migrating + Storwize volume isn't displayed as attached after succesfull migrate due + to retype |
summary: |
- Storwize volume isn't displayed as attached after succesfull migrate due + Storwize volume isn't displayed as attached after successful migrate due to retype |
Changed in cinder: | |
milestone: | juno-2 → juno-3 |
Changed in cinder: | |
milestone: | juno-3 → juno-rc1 |
Changed in cinder: | |
assignee: | git-harry (git-harry) → nobody |
Attach/detach should not be allowed during retype