Red Hat Bugzilla – Bug 1120780
[RFE] Wait for user input to shutdown vm in the end of hosted-engine deployment process
Last modified: 2016-03-09 13:51:58 EST
Description of problem: When you installed engine on hosted-engine-vm, and deployment process checked if engine is available, deployment print line "The system will wait until the VM is down" and wait until user manually will shutdown vm. It was really useful to get to user choice: (1) Shutdown vm automatically (2) Shutdown vm manually (3) Some other options 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. Continue hosted-engine --deploy until you coming to stage "The system will wait until the VM is down" 2. 3. Actual results: Deployment process will wait until user shutdown vm until end of the world without give possibility to user choice to shutdown vm automatically Expected results: Some interact menu that will give to user possibility to choose option to shutdown vm automatically Additional info: Thanks to Lukas Bednar we almost have automatically hosted-engine deployment process, but because this stage not interactive, we still need to shutdown vm manually, so I also set this bug to be AutomationBlocker
targeting to 3.6, I suggest to backport to 3.5.z too.
Auto shutdown may be harmful is some scenarios. The way we'll handle it is by allowing an automation flag in the answer file. So manual installation will show the same text we have today. However, automation using an answer file will be able to add a flag which will auto-shutdown the VM to allow automation completion.
Verified on ovirt-hosted-engine-setup-1.3.0-0.0.master.20150518075146.gitdd9741f.el7.noarch Add line to answer file: OVEHOSTED_VM/automateVMShutdown=bool:True Vm shutdowned automatically.
Adding test coverage flag "-", as there is no need for a test plan.
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