Starting 4.0, the only method to deploy additional hosted-engine hosts to an existing RHV HE deployment should be via RHV UI only, see bz#1255230. `hosted-engine --deploy` is not used any more and not being tested. That's why we should prevent users using it and running into errors. Block this option or add a warning to it, saying that web UI should be used for this operation. Running it at user's own risk and not supported.
(In reply to Marina from comment #0) > Starting 4.0, the only method to deploy additional hosted-engine hosts to an > existing RHV HE deployment should be via RHV UI only, see bz#1255230. > > `hosted-engine --deploy` is not used any more and not being tested. > That's why we should prevent users using it and running into errors. > > Block this option or add a warning to it, saying that web UI should be used > for this operation. Running it at user's own risk and not supported. Just for the record, `hosted-engine --deploy` is still used to deploy the initial host, so the block/warning should happen only when a host is already deployed.
(In reply to Rafael Martins from comment #2) > (In reply to Marina from comment #0) > > Starting 4.0, the only method to deploy additional hosted-engine hosts to an > > existing RHV HE deployment should be via RHV UI only, see bz#1255230. > > > > `hosted-engine --deploy` is not used any more and not being tested. > > That's why we should prevent users using it and running into errors. > > > > Block this option or add a warning to it, saying that web UI should be used > > for this operation. Running it at user's own risk and not supported. > > Just for the record, `hosted-engine --deploy` is still used to deploy the > initial host, so the block/warning should happen only when a host is already > deployed. This should also be used for emergencies and automation so we cannot completely block it but we can advise against using this unless there's a good reason for it.
I've tried to add additional hosted-engine-host using hosted-engine --deploy on additional host and got this warning: [WARNING] Setup of additional hosts using this software is deprecated and will be removed in 4.1. Please use the engine web interface to deploy any additional hosts. The specified storage location already contains a data domain. Is this an additional host setup (Yes, No)[Yes]? Works for me on these components: qemu-kvm-rhev-2.6.0-28.el7_3.1.x86_64 vdsm-4.18.18-1.el7ev.x86_64 ovirt-setup-lib-1.0.2-1.el7ev.noarch ovirt-imageio-common-0.3.0-0.el7ev.noarch sanlock-3.4.0-1.el7.x86_64 ovirt-vmconsole-1.0.4-1.el7ev.noarch mom-0.5.8-1.el7ev.noarch rhev-release-4.0.6-4-001.noarch ovirt-hosted-engine-ha-2.0.6-1.el7ev.noarch ovirt-host-deploy-1.5.3-1.el7ev.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch ovirt-imageio-daemon-0.4.0-0.el7ev.noarch libvirt-client-2.0.0-10.el7.x86_64 ovirt-vmconsole-host-1.0.4-1.el7ev.noarch rhevm-appliance-20161116.0-1.el7ev.noarch ovirt-hosted-engine-setup-2.0.4.1-2.el7ev.noarch Linux version 3.10.0-514.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Wed Oct 19 11:24:13 EDT 2016 Linux 3.10.0-514.el7.x86_64 #1 SMP Wed Oct 19 11:24:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.3 (Maipo)