Confirmed that volumes do appear "attached" to error state instances
(though I couldn't reproduce exactly the steps in the description).
However, Horizon is just displaying the information returned by the nova
API calls (the server info lists the volume, and os-volume-attachments
also lists the volume and its mount point).
** Changed in: horizon
Status: New => Triaged
** Changed in: horizon
Importance: Undecided => Wishlist
** Changed in: horizon
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1278557
Title:
VM instance errors out - shows that it's still attached to volume
Status in OpenStack Dashboard (Horizon):
Won't Fix
Bug description:
== How to Reproduce ==
1. Create an Instance with flavor m1xlarge, then select 'Boot from
Volume'. Pick a volume whose size cannot accommodate the flavor.
2. Launch
==> Instance will go into error state
4. Now click on the instance name to see the Detail view, scroll to
bottom to see it is attached to the volume you selected
5. Now click on that volume to see the Detail view
==> It does not show it is attached to the volume
==> In the Volume table, the volume is shown as "available"
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1278557/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
