Description of problem: Connection to rhevm-appliance vm via serial console not work. Version-Release number of selected component (if applicable): rhevm-appliance-20151108.0-1.el7ev.noarch ovirt-hosted-engine-setup-1.3.0-1.el7ev.noarch How reproducible: Always Steps to Reproduce: 1. Install appliance above 2. Run hosted-engine --deploy 3. Choose installation from disk and continue deploy from appliance 4. Answer no on question: Automatically execute engine-setup on the engine appliance on first boot (Yes, No)[Yes]? No 5. Continue deployment until you come to step [ INFO ] Creating VM You can now connect to the VM with the following command: /bin/remote-viewer vnc://localhost:5900 Use temporary password "3716JOdz" to connect to vnc console. Please note that in order to use remote-viewer you need to be able to run graphical applications. This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding). Otherwise you can run the command from a terminal in your preferred desktop environment. If you cannot run graphical applications you can connect to the graphic console from another host or connect to the serial console using the following command: socat UNIX-CONNECT:/var/run/ovirt-vmconsole-console/43216bb0-439e-4b76-b0c8-845a3b13bc23.sock,user=ovirt-vmconsole STDIO,raw,echo=0,escape=1 If you need to reboot the VM you will need to start it manually using the command: hosted-engine --vm-start You can then set a temporary password using the command: hosted-engine --add-console-password Please install and setup the engine in the VM. You may also be interested in subscribing to "agent" RHN/Satellite channel and installing rhevm-guest-agent-common package in the VM. The VM has been rebooted. To continue please install oVirt-Engine in the VM (Follow http://www.ovirt.org/Quick_Start_Guide for more info). Make a selection from the options below: (1) Continue setup - oVirt-Engine installation is ready and ovirt-engine service is up (2) Power off and restart the VM (3) Abort setup (4) Destroy VM and abort setup (1, 2, 3, 4)[1]: 6. Try to connect from host to vm via serial console socat UNIX-CONNECT:/var/run/ovirt-vmconsole-console/43216bb0-439e-4b76-b0c8-845a3b13bc23.sock,user=ovirt-vmconsole STDIO,raw,echo=0,escape=1 Actual results: Connection just stuck without any output Expected results: Connection succeed and I can configure appliance vm via serial console Additional info: I tried different configuration for serial console(http://www.cyberciti.biz/faq/centos-rhel-6-install-serial-console/), but nothing worked I can also provide environment with vm appliance for future debug.
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 is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag.
Simone, can we actually enforce to use cloud-init when the rhevm appliance is used? That way we prevent the broken flow which is described in comment 0.
Lowering priority, because it's not affecting the main flow.
(In reply to Fabian Deutsch from comment #5) > Simone, can we actually enforce to use cloud-init when the rhevm appliance > is used? > > That way we prevent the broken flow which is described in comment 0. With cloud-init the user can perform different kind of actions on the engine VM (configuring the hostname, network, root password and eventually automatically executing engine-setup) and we are explicitly asking for each of them. Here the user explicitly choose: Automatically execute engine-setup on the engine appliance on first boot (Yes, No)[Yes]? No
Okay, the question is if we want to answer this question silently with Yes, in case of the rhevm-appliance.
(In reply to Fabian Deutsch from comment #8) > Okay, the question is if we want to answer this question silently with Yes, > in case of the rhevm-appliance. Currently we just ask if the user uses the appliance with cloud-init, otherwise it simply doesn't make sense. We are asking cause some user could prefer to manually tweak engine-setup with custom parameters or he could also add additional networks or similar before having host-deploy deploying the host on hosted-engine-setup request.
I'm closing this bug for now. After all the flow where this bug appears is not the main flow. The primary use case is to use the appliance with cloud-init. Please re-open if you think this is necessary.