volume-attach "already attached" and "already detached" are not mutually exclusive
Bug #1414802 reported by
sparr
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Tushar Trambak Gite | ||
OpenStack Compute (nova) |
Confirmed
|
Low
|
Unassigned |
Bug Description
> nova volume-attach 81eef059-
ERROR: Invalid volume: already attached (HTTP 400) (Request-ID: req-1c51a40b-
> nova volume-detach 81eef059-
ERROR: Invalid volume: already detached (HTTP 400) (Request-ID: req-bb99c24e-
I'm trying to resolve a much larger problem with my openstack environment, involving volume exporting, and I ran across this situation. Whatever the tests are for these two messages, they should be mutually exclusive. Maybe a third message is needed, for some intermediate state?
Changed in cinder: | |
assignee: | nobody → Vincent Hou (houshengbo) |
Changed in nova: | |
assignee: | nobody → Vincent Hou (houshengbo) |
Changed in nova: | |
importance: | Undecided → Low |
tags: | added: volumes |
Changed in nova: | |
status: | In Progress → Confirmed |
assignee: | Vincent Hou (houshengbo) → nobody |
Changed in cinder: | |
assignee: | nobody → Tushar Trambak Gite (tushargite96) |
To post a comment you must log in.
Could you give me the detailed steps to reproduce this bug?
Which version of openstack are you using?