Page MenuHomePhabricator

Bullseye VMs have some issue with sssd
Closed, ResolvedPublic


Every bullseye VM I've checked has failures for sssd. The importance of which, I am not sure of yet.

If you run systemctl list-units, you'll see:

● sssd-nss.socket                                                                              loaded failed failed    SSSD NSS Service responder socket
  sssd-pac.socket                                                                              loaded active listening SSSD PAC Service responder socket
● sssd-pam-priv.socket                                                                         loaded failed failed    SSSD PAM Service responder private socket
● sssd-ssh.socket                                                                              loaded failed failed    SSSD SSH Service responder socket
● sssd-sudo.socket                                                                             loaded failed failed    SSSD Sudo Service responder socket

I can still sudo and log in. I have no idea what the real impact of this failure is. Since mounting the sockets are 100% how containers connect to sssd, it may have a bigger effect on k8s workers and things like that in the future. It seemed worth making a ticket and recording the issue at least.

Event Timeline

Change 724003 had a related patch set uploaded (by David Caro; author: David Caro):

[operations/puppet@production] ldap::sssd: Don't specify services on bullseye

Change 724003 merged by David Caro:

[operations/puppet@production] ldap::sssd: Don't specify services on bullseye

Mentioned in SAL (#wikimedia-cloud) [2021-09-28T12:40:48Z] <dcaro> Merged change on sssd for bullseye cloud hosts (T291585)

dcaro claimed this task.