Description of problem: Can't log in to the engine from Cockpit of NGN 4.0. Version-Release number of selected component (if applicable): ovirt-setup-lib-1.0.2-1.el7ev.noarch mom-0.5.4-1.el7ev.noarch ovirt-hosted-engine-ha-2.0.0-1.el7ev.noarch ovirt-hosted-engine-setup-2.0.0.2-1.el7ev.noarch ovirt-vmconsole-1.0.3-1.el7ev.noarch ovirt-host-deploy-1.5.0-1.el7ev.noarch ovirt-engine-sdk-python-3.6.7.0-1.el7ev.noarch sanlock-3.2.4-1.el7.x86_64 qemu-kvm-rhev-2.3.0-31.el7_2.16.x86_64 ovirt-vmconsole-host-1.0.3-1.el7ev.noarch libvirt-client-1.2.17-13.el7_2.4.x86_64 vdsm-4.18.4-2.el7ev.x86_64 Linux version 3.10.0-327.18.2.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) ) #1 SMP Fri Apr 8 05:09:53 EDT 2016 Linux alma03.qa.lab.tlv.redhat.com 3.10.0-327.18.2.el7.x86_64 #1 SMP Fri Apr 8 05:09:53 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 7.2 Beta How reproducible: 100 Steps to Reproduce: 1.Deploy HE on NGN host over NFS. 2.Try logging in to the engine from Cockpit. 3. Actual results: Vdsm execution failed! Please check that: - VDSM is set up properly (i.e. /etc/pki/vdsm/certs/cacert.pem is required) - [path_to_cokcpit-ovirt-plugin]/vdsm/vdsm is executable, VDSM path: /usr/share/cockpit/ovirt-dashboard/vdsm/vdsm/vdsm Expected results: Log in to the engine should succeed. Additional info: Pictures are attached, together with the sosreport from the host.
Created attachment 1172510 [details] login prompt picture
Created attachment 1172515 [details] log in failed error
Sosreport from host available from here: https://drive.google.com/a/redhat.com/file/d/0B85BEaDBcF88dDZMOThTc1pfNFE/view?usp=sharing
Is the provided user/password/engine URL valid? From the attached screenshot, the URL states https://engine.local/... Is the engine really deployed on this location? As a test, try in your browser https://[ENGINE_HOST]/ovirt-engine/ When correct, it will return ovirt login prompt. Please use this URL in the VM management cockpit's login form. For completeness, https://[ENGINE_HOST]/ovirt-engine/api is the entry point for the REST API and it must be working prior connecting to it from the cockpit.
(In reply to Marek Libra from comment #4) > Is the provided user/password/engine URL valid? > > From the attached screenshot, the URL states > https://engine.local/... > Is the engine really deployed on this location? > > As a test, try in your browser > https://[ENGINE_HOST]/ovirt-engine/ > > When correct, it will return ovirt login prompt. > Please use this URL in the VM management cockpit's login form. > > For completeness, > https://[ENGINE_HOST]/ovirt-engine/api > is the entry point for the REST API and it must be working prior connecting > to it from the cockpit. I've changed the URL to real one "https://nsednev-he-1.qa.lab.tlv.redhat.com/ovirt-engine/" and logged in successfully, but I don't understand why it's not provided by the system, it's known as host is part of hosted-engine environment. BTW, setting host in to maintenance after logged in to the engine also fails: "Switch host to maintenance failed Engine not accessible Login to Engine not available. Please confirm all VMs on this host will be shut down" and this: "getAllVmsList() error: 405" VMs in Cluster also shows: "getAllVmsList() error: 405 ".
Did you confirm to shutdown all VMs after failed 'Host to Maintenance'? If so, all VMs running on the host went down, most probably including the Hosted Engine VM. This is what the 'Host to Maintenance' do: - call engine to switch the host to maintenance - if it fails (like no engine login available or action execution/validation fails): then the user is informed and has an option to shutdown all VMs witjout involving the engine - host-local only action.
(In reply to Marek Libra from comment #6) > Did you confirm to shutdown all VMs after failed 'Host to Maintenance'? > > If so, all VMs running on the host went down, most probably including the > Hosted Engine VM. > > This is what the 'Host to Maintenance' do: > - call engine to switch the host to maintenance > - if it fails (like no engine login available or action execution/validation > fails): > then the user is informed and has an option to shutdown all VMs witjout > involving the engine - host-local only action. I have not even a single guest VM on my system.
I've successfully logged in to the engine from Cockpit on my RHEVH, had not seen any errors as appeared before. Works for me on these components: Engine: ovirt-engine-dwh-setup-4.0.1-1.el7ev.noarch ovirt-engine-dwh-4.0.1-1.el7ev.noarch [root@nsednev-he-1 ~]# rpm -qa | grep ovirt ovirt-engine-websocket-proxy-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-extensions-api-impl-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-userportal-4.0.2-0.1.rc.el7ev.noarch ovirt-iso-uploader-4.0.0-1.el7ev.noarch ovirt-engine-dbscripts-4.0.2-0.1.rc.el7ev.noarch ovirt-vmconsole-proxy-1.0.4-1.el7ev.noarch ovirt-engine-setup-plugin-ovirt-engine-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-vmconsole-proxy-helper-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-webadmin-portal-debuginfo-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-tools-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-webadmin-portal-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-cli-3.6.7.0-1.el7ev.noarch ovirt-vmconsole-1.0.4-1.el7ev.noarch ovirt-setup-lib-1.0.2-1.el7ev.noarch ovirt-engine-setup-base-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-setup-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-tools-backup-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-dashboard-1.0.1-0.el7ev.x86_64 ovirt-engine-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-sdk-python-3.6.7.0-1.el7ev.noarch ovirt-log-collector-4.0.0-1.el7ev.noarch ovirt-engine-lib-4.0.2-0.1.rc.el7ev.noarch ovirt-host-deploy-java-1.5.1-1.el7ev.noarch ovirt-engine-dwh-setup-4.0.1-1.el7ev.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-userportal-debuginfo-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-backend-4.0.2-0.1.rc.el7ev.noarch ovirt-engine-dwh-4.0.1-1.el7ev.noarch ovirt-engine-setup-plugin-websocket-proxy-4.0.2-0.1.rc.el7ev.noarch python-ovirt-engine-sdk4-4.0.0-0.5.a5.el7ev.x86_64 ovirt-engine-restapi-4.0.2-0.1.rc.el7ev.noarch ovirt-image-uploader-4.0.0-1.el7ev.noarch ovirt-host-deploy-1.5.1-1.el7ev.noarch ovirt-engine-extension-aaa-jdbc-1.1.0-1.el7ev.noarch rhev-guest-tools-iso-4.0-4.el7ev.noarch rhevm-4.0.2-0.1.rc.el7ev.noarch rhev-release-4.0.2-1-001.noarch rhevm-doc-4.0.0-3.el7ev.noarch rhevm-spice-client-x86-msi-4.0-2.el7ev.noarch rhevm-branding-rhev-4.0.0-3.el7ev.noarch rhevm-spice-client-x64-msi-4.0-2.el7ev.noarch rhevm-guest-agent-common-1.0.12-2.el7ev.noarch rhevm-dependencies-4.0.0-1.el7ev.noarch rhevm-setup-plugins-4.0.0.1-1.el7ev.noarch rhev-release-4.0.1-2-001.noarch Linux version 3.10.0-327.22.2.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) ) #1 SMP Thu Jun 9 10:09:10 EDT 2016 Linux 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 9 10:09:10 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.2 (Maipo) Host: rhevm-appliance-20160714.0-1.el7ev.noarch sanlock-3.2.4-2.el7_2.x86_64 ovirt-hosted-engine-ha-2.0.1-1.el7ev.noarch ovirt-imageio-daemon-0.3.0-0.el7ev.noarch ovirt-host-deploy-1.5.1-1.el7ev.noarch ovirt-engine-sdk-python-3.6.7.0-1.el7ev.noarch qemu-kvm-rhev-2.3.0-31.el7_2.16.x86_64 mom-0.5.5-1.el7ev.noarch ovirt-setup-lib-1.0.2-1.el7ev.noarch ovirt-vmconsole-host-1.0.4-1.el7ev.noarch libvirt-client-1.2.17-13.el7_2.5.x86_64 vdsm-4.18.6-1.el7ev.x86_64 ovirt-hosted-engine-setup-2.0.1-1.el7ev.noarch ovirt-imageio-common-0.3.0-0.el7ev.noarch ovirt-vmconsole-1.0.4-1.el7ev.noarch Linux version 3.10.0-327.22.2.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) ) #1 SMP Thu Jun 9 10:09:10 EDT 2016 Linux 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 9 10:09:10 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 7.2
Given I experienced the same issue on RHV 4 here, what is the workaround until this issue has been fixed?
Robert, please make sure the entered engine URL is correct, format: https://[ENGINE_HOST]/ovirt-engine Of course, check the credentials. To verify, try in browser: https://[ENGINE_HOST]/ovirt-engine/api It should successfully return XML document. If the given connection details are correct but connection still not working, please make sure the engine URL (port 443) is accessible from the host itself - check firewall, DNS, etc.
Marek, thank you very much for your reply - however this is unfortunately not the solution in my case through. I filed bug #1374873 now, because the ovirt-engine never replies to the Apache reverse proxy due to Java errors.
Test version: redhat-virtualization-host-4.0-20160919.0 imgbased-0.8.5-0.1.el7ev.noarch cockpit-ws-0.114-2.el7.x86_64 cockpit-ovirt-dashboard-0.10.6-1.4.0.el7ev.noarch ovirt-hosted-engine-setup-2.0.2.2-2.el7ev.noarch ovirt-hosted-engine-ha-2.0.4-1.el7ev.noarch rhevm-appliance-20160922.0-1.el7ev.ova Test steps: 1.Deploy HE on NGN host over NFS. 2.Try logging in to the engine from Cockpit. Test esults: Login to the engine from Cockpit of RHVH 4.0 can successful. After login, it show as "logout from engine". So the bug is fixed, change bug status to VERIFIED.