Description of problem:
Originally created from the https://bugzilla.redhat.com/show_bug.cgi?id=1211606

Nikolai Sednev 2015-05-04 10:15:41 EDT
RED HAT CONFIDENTIAL
(In reply to Fabian Deutsch from comment #15)
> Sure.
> 
> Please use this ova to verify this bug:
> https://brewweb.devel.redhat.com/buildinfo?buildID=430650

First of all ssh is still blocked to Engine's-VM, please make sure you have correct ssh_config file packaged in to OVF, so after it could be reached from outside after VM being extracted from OVA file:
[nsednev@nsednev ~]$ ssh root.lab.tlv.redhat.com
The authenticity of host 'nsednev-he-2.qa.lab.tlv.redhat.com (10.35.97.250)' can't be established.
RSA key fingerprint is 97:71:d9:49:86:5d:77:d3:02:b7:97:32:6a:ac:d6:a2.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'nsednev-he-2.qa.lab.tlv.redhat.com,10.35.97.250' (RSA) to the list of known hosts.
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
[nsednev@nsednev ~]$


Secondly, after casting "engine-setup --offline --config-append=/root/ovirt-engine-answers" to get engine configured properly, engine web page is up and running (I've logged in to it successfully via my browser, yet there was no host within added, as HE deployment not yet got to the point of adding the host in to the engine), but HE deployment fails to get connectivity to it as shown bellow:

         virsh -c qemu+tls://alma03.qa.lab.tlv.redhat.com/system console HostedEngine
          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.
          To continue make a selection from the options below:
          (1) Continue setup - engine installation is complete
          (2) Power off and restart the VM
          (3) Abort setup
          (4) Destroy VM and abort setup

          (1, 2, 3, 4)[1]:
[ ERROR ] Invalid value
          To continue make a selection from the options below:
          (1) Continue setup - engine installation is complete
          (2) Power off and restart the VM
          (3) Abort setup
          (4) Destroy VM and abort setup

          (1, 2, 3, 4)[1]: 2
[ INFO  ] Creating VM
          You can now connect to the VM with the following command:
                /bin/remote-viewer vnc://localhost:5900
          Use temporary password "2822OgZk" 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 console using the following command:
          virsh -c qemu+tls://alma03.qa.lab.tlv.redhat.com/system console HostedEngine
          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
          To continue make a selection from the options below:
          (1) Continue setup - engine installation is complete
          (2) Power off and restart the VM
          (3) Abort setup
          (4) Destroy VM and abort setup

          (1, 2, 3, 4)[1]:
[ INFO  ] Engine replied: DB Up!Welcome to Health Status!



I've needed to execute option "2" which is powering off the VM and then starting it on again via the deployment procedure as shown above, only then I was able to get the connectivity from host to engine "[ INFO  ] Engine replied: DB Up!Welcome to Health Status!".

Then I've completed all deployment steps and got to the point that it required from me to manually to shut down the engine's VM, I did that via the console, as ssh session is not enabled (please see above) and deployment passed OK.

After a few minutes I've got the "up" status for the VM and connected to it via WEBUI, while ssh was still disabled:


[root@alma03 ~]# hosted-engine --vm-status


--== Host 1 status ==--

Status up-to-date                  : True
Hostname                           : alma03.qa.lab.tlv.redhat.com
Host ID                            : 1
Engine status                      : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "up"}
Score                              : 2400
Local maintenance                  : False
Host timestamp                     : 4942
Extra metadata (valid at timestamp):
        metadata_parse_version=1
        metadata_feature_version=1
        timestamp=4942 (Mon May  4 11:16:23 2015)
        host-id=1
        score=2400
        maintenance=False
        state=EngineStarting
You have new mail in /var/spool/mail/root
[root@alma03 ~]#



[nsednev@nsednev ~]$ ssh root.lab.tlv.redhat.com
ssh: connect to host nsednev-he-2.qa.lab.tlv.redhat.com port 22: Connection refused

Components were used on host:
mom-0.4.1-4.el7ev.noarch
vdsm-4.16.13.1-1.el7ev.x86_64
ovirt-host-deploy-1.3.0-2.el7ev.noarch
qemu-kvm-rhev-2.1.2-23.el7_1.2.x86_64
sanlock-3.2.2-2.el7.x86_64
libvirt-client-1.2.8-16.el7_1.2.x86_64
ovirt-hosted-engine-ha-1.2.5-1.el7ev.noarch
ovirt-hosted-engine-setup-1.2.2-3.el7.noarch

Version-Release number of selected component (if applicable):
mom-0.4.1-4.el7ev.noarch
vdsm-4.16.13.1-1.el7ev.x86_64
ovirt-host-deploy-1.3.0-2.el7ev.noarch
qemu-kvm-rhev-2.1.2-23.el7_1.2.x86_64
sanlock-3.2.2-2.el7.x86_64
libvirt-client-1.2.8-16.el7_1.2.x86_64
ovirt-hosted-engine-ha-1.2.5-1.el7ev.noarch
ovirt-hosted-engine-setup-1.2.2-3.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1.Deploy HE on NFS using OVA and try to get it cofigureed using command "engine-setup --offline --config-append=/root/ovirt-engine-answers"
2.Try to continu with the deployment script of HE deployment and see that you're not succeeding to continue using "(1) Continue setup - engine installation is complete" you must use "(2) Power off and restart the VM" instead and only then use "(1) Continue setup - engine installation is complete".


Actual results:
Customer have to use "(2) Power off and restart the VM" instead of using "(1) Continue setup - engine installation is complete".

Expected results:
After finishing with OVA image, installation should succeed from the very first time with "(1) Continue setup - engine installation is complete".

Additional info: