Description of problem: While deploying ovirt-hosted-engine, administrator is asked about the type of VM installation (cdrom, disk, pxe). If cdrom is selected, and information regarding cd/dvd device node provided, during VM startup deployment will fail, without valid information regarding the cause of failure. Log however contains the following: 2015-07-25 16:00:16 DEBUG otopi.plugins.ovirt_hosted_engine_setup.vm.runvm mixins._create_vm:268 {'status': {'message': 'Done', 'code': 0}, 'statsList': [{'status': 'Down', 'exitMessage': "internal error: early end of file from monitor: possible problem:\n2015-07-25T14:00:16.487075Z qemu-kvm: -drive file=/dev/sr0,if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial=: could not open disk image /dev/sr0: Driver 'host_cdrom' is not whitelisted\n", 'vmId': '*', 'exitReason': 1, 'statusTime': '4296047400', 'exitCode': 1}]} Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.3.0-0.0.master.20150623153111.git68138d4.el7.noarch How reproducible: Always Steps to Reproduce: 1.Run hosted-engine --deploy 2.select cdrom and provide device node path (ie /dev/sr0) Actual results: Deployment fails Expected results: Deployment fails with valid info, or administrator should be warned that CD/DVD passthrough is disabled on RHEL7, and that cdrom option will work only if iso file location is provided. Additional info:
seems HE deployment related, moving to integration
Created attachment 1075508 [details] Warning Took a shot at it, since it was easier to complain on bz. I'm not sure if this is the place to pop this up, or upon selecting cdrom based installation. Kind regards, Ivan
Ivan thanks for the patch! Do you mind pushing it into gerrit? See http://www.ovirt.org/Working_with_oVirt_Gerrit for more info. Feel free to ask on IRC if help is needed with gerrit.
Pushed it as a draft, thanks Sandro, Ivan
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step. If you think this bug should be verified by QE, please set its severity to high and move it back to ON_QA