Bug #4718
Remove devices from boot order list when they are detached (CDROM/DISK/NIC)
| Status: | Closed | Start date: | 08/17/2016 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Sunstone | |||
| Target version: | Release 5.2 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 5.0 |
Description
I attach a cdrom image to a template and change boot order.
After removing the cdrom image, when I try to instantiate the template, one say "Unable to boot disk 1" (cdrom).
So, when the cdrom disk was remove, the boot order is not updated.
Thanks,
Yannick
Associated revisions
Bug #4718: Fix boot order refresh when the removed disk was the only one selected
History
#1
Updated by Ruben S. Montero almost 5 years ago
- Tracker changed from Bug to Backlog
- Subject changed from Boot order issue to Remove devices from boot order list when they are detached (CDROM/DISK/NIC)
- Category set to Core & System
Moved this to the backlog, I consider this more a feature request than a bug
#2
Updated by Yannick MOLINET almost 5 years ago
The image disk is not visible in the UI (boot order).
We must force a change in the boot order and update the template, so it's a bug.
#3
Updated by Yannick MOLINET almost 5 years ago
Error allocating a new virtual machine template. Wrong OS/BOOT value. Device with DISK_ID 1 not found
#4
Updated by Carlos Martín almost 5 years ago
With which OpenNebula version did this happen?
Sunstone is actually supposed to update the boot order when a disk/nic is removed using the "Update VM Template" wizard.
#5
Updated by Yannick MOLINET almost 5 years ago
5.0.2
#6
Updated by Carlos Martín almost 5 years ago
- Tracker changed from Backlog to Bug
- Category changed from Core & System to Sunstone
- Status changed from Pending to Closed
- Assignee set to Carlos Martín
- Target version set to Release 5.2
- Resolution set to fixed
- Affected Versions OpenNebula 5.0 added