-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.7
-
None
-
None
-
Low
-
rhel-plumbers
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
A number of group IDs are hardcoded in systemd.spec, please explain why it's not done like for systemd-coredump group:
%pre getent group cdrom &>/dev/null || groupadd -r -g 11 cdrom &>/dev/null || : getent group utmp &>/dev/null || groupadd -r -g 22 utmp &>/dev/null || : getent group tape &>/dev/null || groupadd -r -g 33 tape &>/dev/null || : getent group dialout &>/dev/null || groupadd -r -g 18 dialout &>/dev/null || : getent group input &>/dev/null || groupadd -r -g 104 input &>/dev/null || : getent group kvm &>/dev/null || groupadd -r -g 36 kvm &>/dev/null || : getent group render &>/dev/null || groupadd -r -g 105 render &>/dev/null || : getent group sgx &>/dev/null || groupadd -r -g 106 sgx &>/dev/null || : getent group systemd-journal &>/dev/null || groupadd -r -g 190 systemd-journal 2>&1 || : getent group systemd-coredump &>/dev/null || groupadd -r systemd-coredump 2>&1 || :
What is the impact of this issue to you?
Customers may have legacy group IDs that may collide with systemd groups being created.
Please provide the package NVR for which the bug is seen:
systemd-252-55.el9_7.7.x86_64
How reproducible is this bug?
N/A
