See e.g. https://gitlab.cee.redhat.com/coreos/redhat-coreos/-/merge_requests/1199#note_1955603. ``` Dec 14 20:16:57.891063 systemd[1]: Starting User Manager for UID 1000... Dec 14 20:16:57.906946 systemd[1897]: pam_unix(systemd-user:session): session opened for user core by (uid=0) Dec 14 20:16:57.950027 systemd[1897]: Failed to fully start up daemon: Permission denied Dec 14 20:16:57.951477 systemd[1899]: pam_unix(systemd-user:session): session closed for user core Dec 14 20:16:57.957096 systemd[1]: user: Failed with result 'protocol'. Dec 14 20:16:57.959203 sshd[1893]: pam_systemd(sshd:session): Failed to create session: Start job for unit user failed with 'failed' Dec 14 20:16:57.957389 systemd[1]: Failed to start User Manager for UID 1000. ``` We've hit it again in the pipeline for `luks.sss.t2`. Seems to happen mostly in `luks.sss.*` tests.
Higher priority work has prevented from this issue being solved; adding UpcomingSprint keyword
Saw this on the `coreos.boot-mirror` test against RHCOS 4.8 most recently
I actually haven't really dug into this this sprint and it's a pretty low occurrence flake AFAICT.
Still haven't sorted this out; moving to 4.9.0
This error might be resolved come RHEL 8.5 - https://bugzilla.redhat.com/show_bug.cgi?id=1946453
Workaround in https://github.com/coreos/coreos-assembler/pull/2261
This feels more like a failure in how our tests are running, so I've copied the failure/error to https://github.com/openshift/os/issues/691 If we find something in the OS that we should fix, we can reopen this.