Red Hat Bugzilla – Bug 1101297
[RFE] Allow fully automatic deployment process for hosted-engine
Last modified: 2016-03-09 13:51:07 EST
Description of problem: Now hosted-engine --deploy process wait input from user, on steps, like OS installation and engine installation. It very useful to make it fully automatically also for testing and also for user it will useful just give answer-file and not wait for each step. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.1.2-5.el6ev.noarch How reproducible: Always Steps to Reproduce: 1. Run hosted-engine --deploy 2. 3. Actual results: Deployment process waiting for user input on stages like OS and engine installation. Expected results: Fully automatic deployment with answer file Additional info: Sandro proposed, something like this: I guess we can just pass 1 to OS setup dialog with an additional env variable: it will wait for VM shutdown before continuing. For the next one we can just add a 5 seconds sleep and pass 1 using the same additional env variable: it will cause an output saying engine is not live and try again after checking its config.(for this option we also need to add some flag to answer file like automatic_deployment, also timeout and sample time values)
is this just for unattended setup for testing? (because for production deployments, the plan is to make this simpler via the hosted-engine guest image as described in https://bugzilla.redhat.com/show_bug.cgi?id=1103409#c2)
It's about the interaction on the host, unrelated to the engine VM stuff. Currently this interaction can't be fully automatic. In principle it can be - we'll need to make the verification questions (OS is setup? engine is setup?) loop until success (probably with some timeout) (as well as making them answerable from the answer file).
*** Bug 1186742 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0375.html