Description of problem: A confusing message is displayed when trying to add a second HE host to a fresh installed and uninitialized environment. This part: "Please upgrade the cluster level to 3.6" The Cluster is already at 4.0 level. This is hard-coded as "3.6". frontend/webadmin/modules/frontend/src/main/resources/org/ovirt/engine/ui/frontend/AppErrors.properties:523:ACTION_TYPE_FAILED_UNMANAGED_HOSTED_ENGINE=Cannot ${action} ${type}. You are using an unmanaged hosted engine VM. Please upgrade the cluster level to 3.6 and wait for the hosted engine storage domain to be properly imported. frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/frontend/AppErrors.properties:530:ACTION_TYPE_FAILED_UNMANAGED_HOSTED_ENGINE=Cannot ${action} ${type}. You are using an unmanaged hosted engine VM. Please upgrade the cluster level to 3.6 and wait for the hosted engine storage domain to be properly imported. frontend/webadmin/modules/userportal-gwtp/src/main/resources/org/ovirt/engine/ui/frontend /AppErrors.properties:528:ACTION_TYPE_FAILED_UNMANAGED_HOSTED_ENGINE=Cannot ${action} ${type}. You are using an unmanaged hosted engine VM. Please upgrade the cluster level to 3.6 and wait for the hosted engine storage domain to be properly imported. backend/manager/modules/dal/src/main/resources/bundles/AppErrors.properties:217:ACTION_TYPE_FAILED_UNMANAGED_HOSTED_ENGINE=Cannot ${action} ${type}. You are using an unmanaged hosted engine VM. Please upgrade the cluster level to 3.6 and wait for the hosted engine storage domain to be properly imported. Version-Release number of selected component (if applicable): all, including latest master upstream. How reproducible: 100% Steps to Reproduce: 1. Fresh install RHV 4.0 Hosted-Engine 2. Don't add initial SD (so hosted_storage is not imported) 3. Try to add HE enabled second host (Hosted-Engine->Deploy) Actual results: "Error while executing action: Cannot add Host. You are using an unmanaged hosted engine VM. Please upgrade the cluster level to 3.6 and wait for the hosted engine storage domain to be properly imported." Expected results: Use the correct CL if the cluster selected during host add.
Instead of: "Error while executing action: Cannot add Host. You are using an unmanaged hosted engine VM. Please upgrade the cluster level to 3.6 and wait for the hosted engine storage domain to be properly imported." We could say: "Error while executing action: Cannot add Host. You are using an unmanaged hosted engine VM. Please add the first Storage Domain in order to start the hosted engine import process" And then also check if CL < required, and display an additional message only if there is a problem with the CL. Right now the message points to CL, but the problem is it's missing the initial SD.
The cluster level checking was removed in Bug 1383156, so this fix only changes the message.
*** Bug 1448808 has been marked as a duplicate of this bug. ***
In latest 4.1.3.1-0.1.el7 engine its not possible to add additional HE-host as there is no such option available, until at least one data storage domain had been added, even first HE-host being shown as regular host. This bug can't be verified while already in 4.1.3.
If the option is not availlable in webadmin, maybe this bug can be tested using REST API. The method for adding hosts can also deploy hosted engine: http://ovirt.github.io/ovirt-engine-api-model/master/#services/hosts/methods/add
(In reply to Andrej Krejcir from comment #8) > If the option is not availlable in webadmin, maybe this bug can be tested > using REST API. The method for adding hosts can also deploy hosted engine: > > http://ovirt.github.io/ovirt-engine-api-model/master/#services/hosts/methods/ > add While using REST-API and trying to add additional hosted-engine-host I've received as follows: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <fault> <detail>[Cannot add Host. You are using an unmanaged hosted engine VM. Please add the first storage domain in order to start the hosted engine import process.]</detail> <reason>Operation Failed</reason> </fault> Moving to verified as it works for me on these components on hosts: ovirt-vmconsole-host-1.0.4-1.el7ev.noarch mom-0.5.9-1.el7ev.noarch ovirt-imageio-daemon-1.0.0-0.el7ev.noarch libvirt-client-2.0.0-10.el7_3.9.x86_64 ovirt-vmconsole-1.0.4-1.el7ev.noarch vdsm-4.19.17-1.el7ev.x86_64 ovirt-hosted-engine-ha-2.1.1-1.el7ev.noarch ovirt-host-deploy-1.6.5-1.el7ev.noarch ovirt-imageio-common-1.0.0-0.el7ev.noarch qemu-kvm-rhev-2.6.0-28.el7_3.10.x86_64 ovirt-hosted-engine-setup-2.1.2-2.el7ev.noarch sanlock-3.4.0-1.el7.x86_64 ovirt-setup-lib-1.1.1-1.el7ev.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch Linux version 3.10.0-514.21.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Sat Apr 22 02:41:35 EDT 2017 Linux 3.10.0-514.21.1.el7.x86_64 #1 SMP Sat Apr 22 02:41:35 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.3 (Maipo) Engine: rhev-guest-tools-iso-4.1-5.el7ev.noarch rhevm-dependencies-4.1.1-1.el7ev.noarch rhevm-4.1.3.1-0.1.el7.noarch rhevm-setup-plugins-4.1.2-1.el7ev.noarch rhevm-branding-rhev-4.1.0-1.el7ev.noarch rhevm-doc-4.1.3-1.el7ev.noarch Linux version 3.10.0-514.16.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Fri Mar 10 13:12:32 EST 2017 Linux 3.10.0-514.16.1.el7.x86_64 #1 SMP Fri Mar 10 13:12:32 EST 2017 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.3 (Maipo)
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://access.redhat.com/errata/RHEA-2017:1692