Bug 958151

Summary:	systemd sysusers inconsistent
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Ludwig Nussel <lnussel>
Component:	Basesystem	Assignee:	systemd maintainers <systemd-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	fbui, lnussel, thomas.blume
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Ludwig Nussel 2015-12-07 08:34:19 UTC

systemd ships several files in /usr/lib/sysusers.d. The information there is not consistent with our defaults in aaa_base though. So please either

- make them consistent and ensure they stay consistent, or
- remove them

Comment 1 Thomas Blume 2015-12-08 13:49:08 UTC

(In reply to Ludwig Nussel from comment #0)
> systemd ships several files in /usr/lib/sysusers.d. The information there is
> not consistent with our defaults in aaa_base though. So please either
> 
> - make them consistent and ensure they stay consistent, or
> - remove them

Hm, I'd assume that aaa_base gets installed before systemd. So there should be no collision as described in the sysusers.d manpage:

-->--
IDEMPOTENCE
Note that systemd-sysusers will do nothing if the specified users or groups already exist, so normally there no reason to override sysusers.d vendor configuration, except to block certain users or groups from being created.
--<--

What is the exact sysuser setting where you saw a problem?

Comment 2 Ludwig Nussel 2015-12-09 03:41:35 UTC

the settings of users are not the same, standard groups have no defined gid etc. 
Yes, that is not a problem as long as aaa_base created all users and groups that are incorrectly listed in systemd as well before. Still, what's the point of shipping incorrect files?

Comment 3 Thomas Blume 2016-01-18 09:52:24 UTC

(In reply to Ludwig Nussel from comment #2)
> the settings of users are not the same, standard groups have no defined gid
> etc. 
> Yes, that is not a problem as long as aaa_base created all users and groups
> that are incorrectly listed in systemd as well before. Still, what's the
> point of shipping incorrect files?

I've build some testpackages with sysusers aligned to the config from aaa_base.
Instead of figuring out an artificial testcase, I'd like to get it verified on the concrete case of this bug. 
I guess you stumbled over a problem that made you discover the mismatch.
Would you mind giving the packages at:

http://download.opensuse.org/repositories/home:/tsaupe:/branches:/openSUSE:/Factory:/boo958151-systemd/openSUSE_Tumbleweed/x86_64/

a try?

Comment 4 Ludwig Nussel 2016-01-18 10:52:45 UTC

I have no concrete case. I ran into this when investigating the offline updates feature gnome tried to sneak in. You can test it by removing some sysuser and messing with the time stamps of /etc/.updated and /usr.

However, your solution does not make sure changes to aaa_base are inherited by systemd. I think it would be a  better idea to generate basic.conf from /var/adm/fillup-templates/passwd.aaa_base

Comment 5 Franck Bui 2017-06-21 15:39:07 UTC

Let's move to the discussion to the other bug.

*** This bug has been marked as a duplicate of bug 1006978 ***