libnss-sss removes config when not being purged
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dh-nss (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Hirsute |
Won't Fix
|
Undecided
|
Unassigned | ||
Impish |
Won't Fix
|
Undecided
|
Unassigned | ||
sssd (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Focal |
Triaged
|
Medium
|
Unassigned | ||
Hirsute |
Won't Fix
|
Medium
|
Unassigned | ||
Impish |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
lsb_release -rdc
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
apt-cache policy libnss-sss
libnss-sss:
Installed: 2.2.3-3ubuntu0.3
Candidate: 2.2.3-3ubuntu0.3
Version table:
*** 2.2.3-3ubuntu0.3 500
500 http://
100 /var/lib/
2.
500 http://
2.2.3-3 500
500 http://
libnss-sss has a postinst script that modifies /etc/nsswitch.conf and adds "sss" to many of the lines. (/var/lib/
After running `apt remove libnss-sss`, the same lines are modified again in /etc/nsswitch.conf to remove the changes.
If you then install libnss-sss again, nsswitch.conf is NOT re-modified on subsequent installs. libnss-sss will only re-modify /etc/nsswitch.conf if it has been purged first / "clean" install.
Expectation: if config is changed *only* during initial install, then config should be left behind during a remove, and config only removed when the package is *purged*.
The only exception I can think of is if there's some specific reason to want to back out the changes to /etc/nsswitch.conf any time libnss-sss is removed (but *not* purged)... and if this is the case, then I'd think maybe the postinst script should be *re-adding* "sss" to nsswitch.conf on *any* install/reinstall (even if it wasn't purged first).
I'm happy to provide any other information needed, but this is my first filed bug so I apologize if I'm lacking. :)
description: | updated |
Changed in sssd (Ubuntu): | |
status: | New → Triaged |
Changed in dh-nss (Ubuntu Focal): | |
status: | New → Invalid |
Changed in dh-nss (Ubuntu): | |
status: | New → Incomplete |
Thanks for the report. I can indeed confirm the bug. I could also verify that the behaviour still happens as of Hirsute.
I've subscribed the Ubuntu Server team to the bug; we will look into it as time permits. This does not seem to be an urgent issue, though, so it may take a while until it is resolved.