Red Hat Bugzilla – Bug 1304650
[RFE] - he-setup should wait for all services and the Engine VM to come up successful at the end of the setup
Last modified: 2017-12-20 05:49:22 EST
Description of problem:
Currently hosted-engine-setup is just starting the services at the end of the setup. But this can lead to the false assumption that everything is working at that point in time.
In reality it takes a while until the services are started and the VM is up and finished booting.
At best he-setup should wait until the services have been started and the VM is up until it ends the setup.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
After successful deployment of ovirt-hosted-engine-setup-2.2.0-0.0.master.20170913082146.git120d800.el7.centos.noarch, while using ovirt-engine-appliance-4.2-20170916.1.el7.centos.noarch, I've got HE-VM powering up and after a few seconds it transited to up and running, I still got to wait a few moments.
HE-VM was not reported as up at the very moment of SHE deployment had finished.
Is this an expected result, e.g. "Feature: Wait for engine vm to power up at the end of Hosted Engine deployment"?
Please see the screencast attached.
Created attachment 1326956 [details]
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.
Works for me on ovirt-hosted-engine-setup-2.2.0-0.0.master.20171016160008.git55723e8.el7.centos.noarch.
Moving to verified.
See also reproduction screencast from https://drive.google.com/a/redhat.com/file/d/0B85BEaDBcF88YkZORExlVTMxZUk/view?usp=sharing
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.
Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.