Bug 1169625

Summary: Issues with vm start up through API
Product: [Retired] oVirt Reporter: punit <hypunit>
Component: ovirt-engine-apiAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.5CC: bugs, ecohen, gklein, hypunit, iheim, lsurette, ofrenkel, rbalakri, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-02 12:41:45 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:

Description punit 2014-12-02 04:54:51 UTC
Description of problem:I am using the ovirt version 3.5 and having some issues with the vm startup with cloud-init using api in run-once mode.....


Version-Release number of selected component (if applicable):
Engine 3.5 (On centos 6.6)
Host On Centos 7.


How reproducible:


Steps to Reproduce:
1. Create the VM by API from precreated OS Template..(Template has boot order priority 1. harddisk 2. Cdrom) 
2. Start the VM in run-once mode and push the cloud-init data from API.. 
3. VM stuck and from console it display the following :- 
Booting from DVD/CD.. ... 
Boot failed : could not read from CDROM (code 004) 

Actual results:Can not Startup the VM..


Expected results: VM will startup and get the cloud-init data from API..


Additional info:I am using the following XML for the API propose...

I am using the following xml for this operation :-

<action>
    <vm>
     <os>
      <boot dev='cdrom'/>    
     </os>
     <initialization>
      <cloud_init>
       <host>
        <address>test</address>
       </host>
       <network_configuration>
        <nics>
         <nic>
          <interface>virtIO</interface> 
          <name>eth0</name>
          <boot_protocol>static</boot_protocol>
          <mac address=''/>
          <network>
           <ip address='' netmask='' gateway=''/>
          </network>
          <on_boot>true</on_boot><vnic_profile id='' />
         </nic>
         <nic>
          <interface>virtIO</interface> 
          <name>eth1</name>
          <boot_protocol>static</boot_protocol>
          <mac address=''/>
          <network>
           <ip address='' netmask='255.255.255.0' gateway=''/>
          </network>
          <on_boot>true</on_boot><vnic_profile id='' />
         </nic>
        </nics>
       </network_configuration>
       <files>
        <file>
         <name>/ignored</name><content><![CDATA[#cloud-config
disable-ec2-metadata: true
disable_root: false
ssh_pwauth: true
ssh_deletekeys: true
chpasswd: { expire: False }

users:
 - name: root
   primary-group: root
   passwd: 8W7RQ5Bh
   lock-passwd: false

runcmd:
 - sed -i '/nameserver/d' /etc/resolv.conf
 - echo 'nameserver 8.8.8.8' >> /etc/resolv.conf
 - echo 'nameserver 8.8.4.4' >> /etc/resolv.conf
 - echo 'root:8W7RQ5Bh' | chpasswd
 - yum -y update
 - yum -y install rdate
 - rdate -s stdtime.gov.hk]]></content>
         <type>plaintext</type>
        </file>
       </files>
      </cloud_init><custom_script><![CDATA[#cloud-config
disable-ec2-metadata: true
disable_root: false
ssh_pwauth: true
ssh_deletekeys: true
chpasswd: { expire: False }

users:
 - name: root
   primary-group: root
   passwd: 8W7RQ5Bh
   lock-passwd: false

runcmd:
 - sed -i '/nameserver/d' /etc/resolv.conf
 - echo 'nameserver 8.8.8.8' >> /etc/resolv.conf
 - echo 'nameserver 8.8.4.4' >> /etc/resolv.conf
 - echo 'root:8W7RQ5Bh' | chpasswd
 - yum -y update
 - yum -y install rdate
 - rdate -s stdtime.gov.hk]]></custom_script>
     </initialization>
    </vm>
   </action>

Comment 1 Omer Frenkel 2014-12-02 07:40:06 UTC
this looks like a duplicate of bug 1169624
am i missing something different here?

Comment 2 punit 2014-12-02 10:03:53 UTC
Hi,

Yes...i just refresh the browser screen...may be added two times...you can remove it or mark it as duplicate...

Comment 3 Gil Klein 2014-12-02 12:41:45 UTC

*** This bug has been marked as a duplicate of bug 1169624 ***