It's not flakyness and it doesn't need to be retried again but debugged. I'm tagged the bug update-excuses
The error it hits is one doing 'systemctl restart sssd', confirmed in a local container env. The journal includes that error
systemd[1]: Starting sssd.service - System Security Services Daemon...
sssd[3784]: SSSD couldn't load the configuration database [1432158246]: No domain is enabled
systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION
Downgrading the sssd packages to the mantic version resolves the issue. It could be a regression or something the tests are doing wrong. I don't plan to investigate more since I don't really know sssd but I hope the details help somehow
A newer version was uploaded but it's blocked in mantic-proposed because it creates a regression for gdm3 autopkgtests
https:/ /autopkgtest. ubuntu. com/packages/ g/gdm3/ mantic/ amd64
It's not flakyness and it doesn't need to be retried again but debugged. I'm tagged the bug update-excuses
The error it hits is one doing 'systemctl restart sssd', confirmed in a local container env. The journal includes that error
systemd[1]: Starting sssd.service - System Security Services Daemon... 4/NOPERMISSION
sssd[3784]: SSSD couldn't load the configuration database [1432158246]: No domain is enabled
systemd[1]: sssd.service: Main process exited, code=exited, status=
Downgrading the sssd packages to the mantic version resolves the issue. It could be a regression or something the tests are doing wrong. I don't plan to investigate more since I don't really know sssd but I hope the details help somehow