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.