Created attachment 898331 [details] loginfo.png Description of problem: Can't login the hypervisor with correct password. Exception: No permission to read file: /etc/pki/vdsm/keys/vdsmkey.pem Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20140521.0.el6ev ovirt-node-3.0.1-18.el6_5.10.noarch ovirt-node-plugin-vdsm-0.1.1-20.el6ev.noarch vdsm-4.14.7-3.el6ev.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install rhev-hypervisor6-6.5-20140521.0.el6ev. 2. After reboot, login the hypervisor with correct password. 3. Please see attachment for more details. Actual results: Can't login the hypervisor with correct password, it will jump to the login screen again. Expected results: login the hypervisor with correct password can successful. Additional info: No such issue with rhev-hypervisor6-6.5-20140513.0(vdsm-4.14.7-2.el6ev.x86_64), so it is a regression bug.
Moving to ovirt-node-plugin-vdsm as this should handle this exception correctly.
"No permission to read file: /etc/pki/vdsm/keys/vdsmkey.pem" This was caused by http://gerrit.ovirt.org/#/c/27779/ (the fix for bug 1097645). Which user runs the the TUI? I think it's safe to add it to the kvm group.
(In reply to Dan Kenigsberg from comment #4) > "No permission to read file: /etc/pki/vdsm/keys/vdsmkey.pem" > > This was caused by http://gerrit.ovirt.org/#/c/27779/ (the fix for bug > 1097645). > > Which user runs the the TUI? I think it's safe to add it to the kvm group. admin user can't login. Enter rescue mode and set password for root user, and then login the hypervisor with root can successful, but run "setup" command can't enter TUI and encounter the original bug again. Thanks!
(In reply to Dan Kenigsberg from comment #4) > "No permission to read file: /etc/pki/vdsm/keys/vdsmkey.pem" > > This was caused by http://gerrit.ovirt.org/#/c/27779/ (the fix for bug > 1097645). > > Which user runs the the TUI? I think it's safe to add it to the kvm group. Just to clarify, what happened: vdscli.py cannot find /etc/pki/vdsm/certs/<files> during the first boot of ovirt-node/before the registration and raised this exception. I have added code to handle the exception and we should be fine. During my previous tests with http://gerrit.ovirt.org/#/c/27779/ I had the files already in the system, that's why I didn't see it before.
Verified this bug on build rhev-hypervisor6-6.5-20140527.0.el6ev ovirt-node-plugin-vdsm-0.1.1-22.el6ev admin user can login RHEV-H, there is no exception happened.
Closing as part of 3.4.0