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.

Description of problem:
The fuse and fuse-libs RPMs were installed as a dependency of Gluster.  Fuse created a group (fuse) for its-self with GID 107.  Trying to install libvirt later errored because 107 is a reserved GID for libvirt.  

The gid selected seems to be random and below 500.  Another install used gid 313.  A third install selected gid 106. 


Version-Release number of selected component (if applicable):
fuse-libs-2.8.3-4.el6.x86_64
fuse-2.8.3-4.el6.x86_64


How reproducible:
Three out of three attempts.


Steps to Reproduce:
1.  yum install -y fuse



Actual results:


Expected results:


Additional info:

Eric,

users/applications are allowed to dynamically create system groups between the range specific for that.

Fuse dynamically create fuse group inside the range allowed by the system, where, in Red Hat Enterprise Linux 6, the default range for dynamically allocated GIDs starts at GID 201, reserving the first 200 GIDs for statically allocated groups (like qemu group at gid 107).

There is no bug here since fuse group is being dynamically allocate based on system's configuration.

Please check your /etc/login.defs and check if the variable SYS_GID_MIN is set for anything below 201.

Feel free to re-open the bug in case you find something misbehaving according to the expected behavior above.

-Carlos