I see the same thing on a test cluster. I presumed it was due to using
sssd and kerberos for local user logins.
Here's an example of what gets written to /var/log/secure when root login
to cockpit fails.
May 18 11:29:07 br014 unix_chkpwd[26429]: check pass; user unknown
May 18 11:29:07 br014 unix_chkpwd[26430]: check pass; user unknown
May 18 11:29:07 br014 unix_chkpwd[26430]: password check failed for user
(root)
May 18 11:29:07 br014 cockpit-session[26427]: pam_unix(cockpit:auth):
authentication failure; logname= uid=993 euid=993 tty= ruser=
rhost=::ffff:128.182.79.36 user=root
May 18 11:29:07 br014 cockpit-session[26427]: pam_succeed_if(cockpit:auth):
requirement "uid >= 1000" not met by user "root"
The uid test is obviously an issue. not sure why check pass seems to always
give user unknown errors. tried putting selinux in permissive same issue.
On Tue, May 18, 2021 at 10:50 AM Glenn Farmer <glenn.farmer(a)netfortris.com>
wrote:
The current thread is about 4.4.6 - nice that you can login to your
4.4.5.
I changed the admin password on the engine - still cannot access the
Cockpit GUI on any of my hosts.
Do I have to reboot them? Restart Cockpit - tried that - failed.
Cannot access Cockpit on all hosts in a cluster after upgrading to 4.4.6
really should be considered a bug.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VZPGTQUWDUP...