Feature #3158
Force CONTEXT to be the last CDROM
| Status: | Closed | Start date: | 08/22/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.10 | |||
| Resolution: | fixed | Pull request: |
Description
As reported on the mailing-list, user must ensure that bootable ISO has a defined TARGET=hda or the CONTEXT CDROM will be tried as bootable device and fails.
Forcing the CONTEXT CDROM to be the last hd device will remove this constraint.
Regards.
Associated revisions
Feature #3158: Force CONTEXT to be the last CDROM
History
#1
Updated by Stefan Kooman almost 7 years ago
+1
Once in a while this issue crops up on the mailing-list, especially newcomers don't expect this behaviour.
#2
Updated by Ruben S. Montero almost 7 years ago
I do not see any problems from an OpenNebula standpoint. Let me check if there is any problem with the contextualization process and cloudinit. From the guest mounting always hda is trivial, don't know if cloudinit or equivalent allows you to pick up the "last" CDROM.
We are going to work on improving the cloudinit support, so we can address this to.
#3
Updated by Javi Fontan almost 7 years ago
- Tracker changed from Request to Feature
- Target version set to Release 4.10
Both OpenNebula context packages and cloud-init look for a CD with label "CONTEXT". The order of the context CD should not be a problem.
#4
Updated by Ruben S. Montero almost 7 years ago
- Category set to Core & System
#5
Updated by Ruben S. Montero almost 7 years ago
- Assignee set to Ruben S. Montero
#6
Updated by Carlos Martín over 6 years ago
- Assignee changed from Ruben S. Montero to Carlos Martín
#7
Updated by Ruben S. Montero over 6 years ago
- Status changed from Pending to Closed
- Resolution set to fixed