Bug 1064927
| Summary: | wrong boot order when trying to boot from CDROM while using cloud-init | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Sven Kieske <s.kieske> |
| Component: | ovirt-engine-core | Assignee: | Shahar Havivi <shavivi> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | bugs <bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.3 | CC: | ecohen, gklein, iheim, mgoldboi, michal.skrivanek, rbalakri, s.kieske, yeylon |
| Target Milestone: | --- | ||
| Target Release: | 3.4.4 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | virt | ||
| Fixed In Version: | ovirt-3.5.0-alpha1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-09-24 08:08:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
These bugs might be related (somewhat): https://bugzilla.redhat.com/show_bug.cgi?id=809457 https://bugzilla.redhat.com/show_bug.cgi?id=809733 Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc. i's getting too late for 3.4 so this may need to wait for 3.4.z, let's see how investigation goes What does the xml looks like when you boot without the cloud-init? Can you boot from the cdrom? From my testing the cdrom doesn't get the boot-order=1 when there is no cloud-init but hte hdd does get boot-order=2 This bug is true for VmPayload as well, The reason is because we are setting the boot order to the first CDROM that is found in the list. This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1. Could this simple patch still get included in 3.4.0 before GA? it's not yet even in master, and 3.4 RC is out and GA is imminent I don't see it likely. If it really blocks something feel free to bring it up on ovirt weekly correction - it's MODIFIED in 3.5 by popular demand, let's backport it to 3.4.z :-) (setting target release) 3.4.3 RC is out so this needs to wait for 3.4.4 oVirt 3.4.4 has been released. |
Description of problem: if you attach a cd-rom via run once and make it the primary boot device and you submit in the same step cloud-init data the xml file generated by ovirt looks like the following: both virtual cd roms get attached and show up in the xml the expected primary boot device shows up as: <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> with no entity (which it should have): <boot order='1'/> the cloud-init data shows up as the following: <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/var/run/vdsm/payload/934aebfd-7a7b-4c47-91be-97d58fb32b1e.34f0c17686175ad722c3b0a03f3db4d3.img' startupPolicy='optional'/> <target dev='hdd' bus='ide'/> <readonly/> <serial></serial> <boot order='1'/> the hdd gets "boot order='2'" this results in a wrong boot order: the vm trys to start from the cloud-init cd rom and fails and then boots the hdd. Tested with the following versions: rpm -qa vdsm vdsm-4.12.1-4.el6.x86_64 rpm -qa ovirt-engine ovirt-engine-3.3.2-1.el6.noarch Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: I'm not able to boot from a cd-rom while passing cloud-init data to the vm Expected results: I can boot from cd Additional info: The bug may be filed against the wrong component, I don't know if ovirt-engine messes this up or maybe vdsm. I also do not know if this is a regression as I never tested this before.