Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This bug was initially created as a copy of Bug #1986111
I am copying this bug because:
Description of problem:
When using groupdel with a prefix path, it segfaults on Fedora 34.
groupadd and groupmod both are working fine.
Version-Release number of selected component (if applicable):
shadow-utils-4.6-12.el8.x86_64
How reproducible:
Every time groupdel is executed (as root)
Steps to Reproduce:
1. Create a custom /etc/group file, e.g. using
[root@rhel84-vm ~]# mkdir -p $HOME/custom_root/etc/
[root@rhel84-vm ~]# touch $HOME/custom_root/etc/group
2. Create a group (succeeds)
[root@rhel84-vm ~]# groupadd -P $HOME/custom_root test_group
3. Delete the group (fails)
[root@rhel84-vm ~]# groupdel -P $HOME/custom_root test_group
Actual results:
[root@rhel84-vm ~]# groupdel -P $HOME/custom_root test_group
Segmentation fault (core dumped)
Expected results:
Return code 0 with the group deleted from $HOME/custom_root/etc/group
After trying some things today it seems that this is related to the existence of a 'passwd' file next to the group file. This because 'groupdel' can then check whether a group is used as primary group. After creating the passwd file (touch $HOME/custom_root/etc/passwd) the groupdel -P command succeeds.
I think there are two options here:
1. Have groupdel output some logging that the passwd file needs to exist
2. Update groupdel to not fail on the absence of a passwd file and just assume that there are no users using the group as primary group.
I'd go with option 2 here, since groupdel then doesn't require a passwd file to continue operating. In case the file doesn't exist, IMO it can be safely said that the group is also not used as primary group for any users (since there are no users).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (shadow-utils bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:2021