bootc 1.1.6 lints are failing due to missing systemd-sysusers entires on upstream packaging

[tulilirockz]

We are running into both bootc getting mad at files existing in /var (we can just delete /var and re-create it being empty) and the following:

Lint warning: sysusers: Found /etc/passwd entry without corresponding systemd sysusers.d:
  avahi
  libstoragemgmt
  setroubleshoot
  wsdd
Found /etc/group entry without corresponding systemd sysusers.d:
  avahi
  libstoragemgmt
  power
  setroubleshoot
  sudo
  ...and 1 more

We need to PR sysusers entries for a few upstream packages else we will run into this forever, heres an example PR from Timothee Ravier: https://src.fedoraproject.org/rpms/flatpak/pull-request/8. This needs to be replicated for avahi, libstoragemgmt, setroubleshoot and wsdd in both the centos-stream RPMs and fedora packaging.

TRACKING

CentOS fixes

• avahi
• libstoragemgmt
• setroubleshoot
• sudo
• upower? - We need to figure out something that adds the power group.
• wsdd

Fedora fixes

• avahi
• libstoragemgmt
• setroubleshoot
• sudo
• upower
• wsdd

[p5]

Another option might be to wait and see how the new bootc container finalize will handle these.
Missing sysusers entries might be generated for us as part of the command.

I don't think RedHat expects all their customers to be PRing these things upstream, so it wouldn't surprise me if they already have a plan for this. If the plan turns out to be fix everything themselves, then let's help out :)

[p5]

@tulilirockz Do you have a link to where we can see these logs?
I don't believe they are present in the latest GitHub Actions builds

[cgwalters]

For sudo, see https://gitlab.com/fedora/bootc/base-images/-/merge_requests/94

For the rest, https://lists.fedoraproject.org/archives/list/[email protected]/thread/RYQRILDUQ4KTTVOQPFADFMLXYQ4GDORC/#J6FI5DBXQ7IQU7HUSPZVN7PESKDRQS53 is happening.

There's a long tail of this stuff for sure though and it will take a bit to make its way to c10s.

Note that none of this is a new problem per se, and in general right now as long as those users are part of the initially provisioned image it's usually OK.