Boot from Volume Still Requires Image
Bug #1163566 reported by
Joe T
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Sam Stoelinga | ||
Bug Description
Hello,
Bug #1008622 allowed volumes to be booted without having to specify an image id. However, Horizon still requests that the user choose an image from the drop-down box when booting from a volume.
I've verified this is happening with Grizzly rc1.
Please let me know if you need any more information.
Thanks,
Joe
| Changed in horizon: | |
| status: | New → Confirmed |
| Changed in horizon: | |
| importance: | Undecided → Medium |
| milestone: | none → havana-1 |
Revision history for this message
| Sam Stoelinga (sammiestoel) wrote | #1 |
| Changed in horizon: | |
| assignee: | nobody → Sam Stoelinga (sammiestoel) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to horizon (master) | #2 |
| Changed in horizon: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to horizon (master) | #3 |
| Changed in horizon: | |
| status: | In Progress → Fix Committed |
| Changed in horizon: | |
| status: | Fix Committed → Fix Released |
| Changed in horizon: | |
| milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
When booting from Volume, the user shouldn't be allowed to choose an Image at all or should we still allow this? I think we shouldn't, doesn't make too much sense, for example maybe he chooses an Ubuntu image with kernel and ramdisk seperated, but his Volume that he's booting from may be a totally different OS. Seems weird.