Description of problem: Engine VM doesn't start deploying from disk or appliance Version-Release number of selected component (if applicable): 3.6.0 master How reproducible: 100% Steps to Reproduce: 1. try to deploy from disk 2. 3. Actual results: it always fails with: [ INFO ] Creating VM [ ERROR ] Failed to execute stage 'Closing up': The VM is not powering up: please check VDSM logs [ INFO ] Stage: Clean up In the VDSM logs you can find: Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 1207, in _startUnderlyingVm self._run() File "/usr/share/vdsm/virt/vm.py", line 2208, in _run domxml = hooks.before_vm_start(self._buildDomainXML(), self.conf) File "/usr/share/vdsm/virt/vm.py", line 2027, in _buildDomainXML return domxml.toxml() File "/usr/share/vdsm/virt/vmxml.py", line 459, in toxml return self.doc.toprettyxml(encoding='utf-8') File "/usr/lib64/python2.7/xml/dom/minidom.py", line 58, in toprettyxml self.writexml(writer, "", indent, newl, encoding) File "/usr/lib64/python2.7/xml/dom/minidom.py", line 1752, in writexml node.writexml(writer, indent, addindent, newl) File "/usr/lib64/python2.7/xml/dom/minidom.py", line 817, in writexml node.writexml(writer, indent+addindent, addindent, newl) File "/usr/lib64/python2.7/xml/dom/minidom.py", line 807, in writexml _write_data(writer, attrs[a_name].value) File "/usr/lib64/python2.7/xml/dom/minidom.py", line 296, in _write_data data = data.replace("&", "&").replace("<", "<"). \ AttributeError: 'int' object has no attribute 'replace' Expected results: it deploys the VM Additional info:
Please check if this affects also 3.5.
(In reply to Sandro Bonazzola from comment #1) > Please check if this affects also 3.5. The issue it that we were handling MEM_SIZE_MB as an int while VDSM expects a string and so we get weird behavior. In 3.5 it wasn't a problem cause we generated a config file via a template for vdsClient and so we had implicit string conversion. In 3.6 we are using vdscli and so we are skipping the temporary file from the template and from there the issue. The only possible issue still open is if you run 3.6 deploy script with an answer file wrongly generated by 3.5. I'm going to fix it also converting wrong types from previously generated answer files.
Ok, moving back to post then, waiting for the new patches.
Hi Simone, Can you please provide the link to OVA or ISO image with 3.6 engine appliance, so I could verify this bug?
You can download master OVA from here: http://jenkins.ovirt.org/view/00%20Unstable%20Jobs%20(Production)/job/ovirt-appliance-engine_master_merged/
You need to use cloud-init to set engine password on the appliance; no default password. The web-admin will not run till you run engine-setup on the appliance to configure it; with a recent (today - https://gerrit.ovirt.org/#/c/40546/ ) patch you could do it automatically from hosted-engine via cloud-init on the first boot. Having a running VM is enough to verify this.
(In reply to Simone Tiraboschi from comment #7) > You need to use cloud-init to set engine password on the appliance; no > default password. > > The web-admin will not run till you run engine-setup on the appliance to > configure it; with a recent (today - https://gerrit.ovirt.org/#/c/40546/ ) > patch you could do it automatically from hosted-engine via cloud-init on the > first boot. > > Having a running VM is enough to verify this. Then lets close this one as verified.
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.