No error displayed on volume attachment fail (need to get errors that happen after initial response)
Bug #970693 reported by
Tihomir Trifonov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Opinion
|
Wishlist
|
Unassigned |
Bug Description
When trying to attach a volume over existing device (i.e we have an instance with disk volume, and we try to attach another volume on /dev/hda) :
The operation finished without the actual error, just the notification above for starting the process. In the table below the status changes from 'Attaching' back to 'Available'. without showing a reason for attachment failure reason.
Changed in horizon: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → folsom-1 |
Changed in horizon: | |
assignee: | nobody → Nebula (nebula) |
Changed in horizon: | |
milestone: | folsom-1 → folsom-2 |
summary: |
- No error is displayed on volume attachment failure + No error displayed on volume attachment fail (need to get errors that + happen after initial response) |
Changed in nova: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
tags: | added: volume |
Changed in horizon: | |
importance: | Medium → Wishlist |
To post a comment you must log in.
We have the same issue. The volume can be only managed using command-line and ID. When we are trying to use volume name (while deleting/attaching volume) then we have the same error as above.