Description of problem: During add additional hosted-engine host via WEBUI I've received this message: "Host (fqdn of my host) uses not compatible protocol during activation (xmlrpc instead of jsonrpc). Please examine installation logs and VDSM logs for failures and reinstall the host.". Version-Release number of selected component (if applicable): Host: qemu-kvm-rhev-2.3.0-31.el7_2.14.x86_64 ovirt-hosted-engine-ha-2.0.0-1.el7ev.noarch mom-0.5.4-1.el7ev.noarch ovirt-vmconsole-host-1.0.3-1.el7ev.noarch ovirt-host-deploy-1.5.0-1.el7ev.noarch ovirt-engine-sdk-python-3.6.5.0-1.el7ev.noarch libvirt-client-1.2.17-13.el7_2.5.x86_64 sanlock-3.2.4-2.el7_2.x86_64 ovirt-setup-lib-1.0.2-1.el7ev.noarch vdsm-4.18.1-11.gita92976e.el7ev.x86_64 ovirt-hosted-engine-setup-2.0.0-1.el7ev.noarch ovirt-vmconsole-1.0.3-1.el7ev.noarch Linux alma03.qa.lab.tlv.redhat.com 3.10.0-327.22.1.el7.x86_64 #1 SMP Mon May 16 13:31:48 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Linux version 3.10.0-327.22.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) ) #1 SMP Mon May 16 13:31:48 EDT 2016 Red Hat Enterprise Linux Server release 7.2 (Maipo) Engine: rhevm-4.0.0.2-0.1.el7ev.noarch rhevm-guest-agent-common-1.0.12-1.el7ev.noarch rhevm-branding-rhev-4.0.0-0.0.master.20160531161414.el7ev.noarch rhevm-dependencies-4.0.0-1.el7ev.noarch rhevm-setup-plugins-4.0.0-1.el7ev.noarch rhevm-doc-4.0.0-2.el7ev.noarch ovirt-engine-setup-plugin-ovirt-engine-4.0.0.2-0.1.el7ev.noarch ovirt-vmconsole-1.0.3-1.el7ev.noarch ovirt-engine-extension-aaa-jdbc-1.1.0-1.el7ev.noarch ovirt-engine-setup-base-4.0.0.2-0.1.el7ev.noarch ovirt-engine-websocket-proxy-4.0.0.2-0.1.el7ev.noarch ovirt-image-uploader-4.0.0-1.el7ev.noarch ovirt-engine-backend-4.0.0.2-0.1.el7ev.noarch ovirt-engine-tools-4.0.0.2-0.1.el7ev.noarch ovirt-engine-lib-4.0.0.2-0.1.el7ev.noarch ovirt-engine-dwh-setup-4.0.0-2.el7ev.noarch ovirt-log-collector-4.0.0-1.el7ev.noarch ovirt-engine-vmconsole-proxy-helper-4.0.0.2-0.1.el7ev.noarch ovirt-host-deploy-java-1.5.0-1.el7ev.noarch ovirt-engine-dbscripts-4.0.0.2-0.1.el7ev.noarch ovirt-engine-4.0.0.2-0.1.el7ev.noarch ovirt-engine-setup-plugin-websocket-proxy-4.0.0.2-0.1.el7ev.noarch ovirt-engine-tools-backup-4.0.0.2-0.1.el7ev.noarch ovirt-engine-userportal-4.0.0.2-0.1.el7ev.noarch ovirt-engine-setup-4.0.0.2-0.1.el7ev.noarch ovirt-vmconsole-proxy-1.0.3-1.el7ev.noarch ovirt-engine-restapi-4.0.0.2-0.1.el7ev.noarch ovirt-engine-cli-3.6.2.0-1.el7ev.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.0.0.2-0.1.el7ev.noarch ovirt-engine-extensions-api-impl-4.0.0.2-0.1.el7ev.noarch ovirt-iso-uploader-4.0.0-1.el7ev.noarch ovirt-engine-webadmin-portal-4.0.0.2-0.1.el7ev.noarch ovirt-engine-dwh-4.0.0-2.el7ev.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.0.0.2-0.1.el7ev.noarch ovirt-host-deploy-1.5.0-1.el7ev.noarch ovirt-setup-lib-1.0.2-1.el7ev.noarch ovirt-engine-sdk-python-3.6.5.0-1.el7ev.noarch Linux version 3.10.0-327.22.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) ) #1 SMP Mon May 16 13:31:48 EDT 2016 Linux 3.10.0-327.22.1.el7.x86_64 #1 SMP Mon May 16 13:31:48 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.2 (Maipo) How reproducible: 100% Steps to Reproduce: 1.Deploy HE over NFS on at least one host and attach one data storage domain. 2.Add additional hosted-engine-host via WEBUI. 3. Actual results: Host (fqdn of my host) uses not compatible protocol during activation (xmlrpc instead of jsonrpc). Please examine installation logs and VDSM logs for failures and reinstall the host. Expected results: No errors should be posted. Additional info: sosreport from the engine and host attached.
Created attachment 1165258 [details] sosreport from host
Created attachment 1165271 [details] sosreport from engine
Regression?
Dup of bug 1343112 ?
(In reply to Yaniv Kaul from comment #4) > Dup of bug 1343112 ? Looks like it is.
Returning back need info that was set in comment #5 by Fabian, that I've accidentally removed.
Let's use a single bz for the same issue. *** This bug has been marked as a duplicate of bug 1343112 ***