Description of problem:
Provisioning from RHEVM 3.6 template loses template boot sequence.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 184.108.40.206-0.1.el6
Steps to Reproduce:
1. Create template with second device in boot sequence
2. Deploy new VM from this template (from CF)
3. Second device is missing in newly provisioned VM
I was able to build a template with 2 devices in the boot sequence - The first was a PXE network device. The second - a block device.
Upon digging into the ovirt gem - I found that there isn't a way for the Disk class to see a device named "network" as the first device list is - So when listing disks in the template at provisioning - The 1st boot device in this case never gets created.
So I was able to duplicate the issue with 2 boot devices, one not being a harddisk.
I have a couple of other questions regarding the problem in general:
1. If the template in question had 2 block devices (dev="hd") it seems that this bug wouldn't exist? - Are you seeing that in your environment?
2. Looking at the ovirt gem - it seems that the ("network" device being first in the boot order) issue would exist for any version of RHEV and not only 3.6 - Are you seeing that in your environment?
I have tested the scenarios and through CloudForms, a VM is provisioned without the boot order set in the source template, regardless of number of disks.
Through RHEV, the provisioning of a new VM always includes the template boot order.
Martin, can you please add PR link?
PR to the ovirt gem: https://github.com/ManageIQ/ovirt/pull/61
Commit that bumps the ovirt gem version to one that includes the above fix: https://github.com/ManageIQ/manageiq/commit/e1009e0ee38e2bf9eac0ed85e26736ddbba4047b
Template rhel-guest-image-7.2-20160302.0.x86_64 with Boot sequense
First device: "network"
Provision VM from template from CF side ends up successfully.
VM indeed was created on RHEVM, and also was started.