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.
DescriptionParikshit Khedekar
2020-07-14 15:56:37 UTC
+++ This bug was initially created as a clone of Bug #1856881 +++
Description of problem:
Updating the nfs-utils modifies the /etc/group file. This is not expected if the package is already installed and the 'rpcuser' group is already there.
The if statement for the nfsnobody seems to be fine but the code for rpcuser needs enhancements as,
The problem is with the prescript of the rpm as,
Current spec file:
~~~~~~~~~
# Create rpcuser gid as long as it does not already exist
cat /etc/group | cut -d':' -f 1 | grep --quiet rpcuser 2>/dev/null
if [ "$?" -eq 1 ]; then
/usr/sbin/groupadd -g 29 rpcuser >/dev/null 2>&1 || :
else
/usr/sbin/groupmod -g 29 rpcuser >/dev/null 2>&1 || :
fi
~~~~~~~~~
Here even the conditions falses the same command is marked to get executed.
The changes to the spec file should be as for modifying/changing the pre-scripts as,
~~~~~~~~~
# Create rpcuser gid as long as it does not already exist
cat /etc/group | cut -d':' -f 1 | grep --quiet rpcuser 2>/dev/null
if [ "$?" -eq 1 ]; then
/usr/sbin/groupadd -g 29 rpcuser >/dev/null 2>&1 || :
fi
~~~~~~~~~
Version-Release number of selected component (if applicable):
RHEL 8/RHEL7
Any release of nfs-utils
How reproducible:
#stat /etc/group -->> check file stamp before update of package.
#yum update nfs-utils
#stat /etc/group -->> check file stamp after update of package.
Steps to Reproduce:
1. check time stamp of the /etc/group file
2. Update the nfs-utils package
3. Check time stamp of the /etc/group file which differs
Actual results:
It does modifies the file unnecessorily.
Expected results:
It should not run the command again if the
Additional info:
There's no further minor releases scheduled for RHEL7 and thus it's very unlikely nfs-utils will be updated, except for an exceptional situation, and this means one of the primary necessary conditions for this bug (an update of nfs-utils) is much less likely in RHEL7.
When Red Hat shipped 7.7 on Aug 6, 2019 Red Hat Enterprise Linux 7 entered Maintenance Support 1 Phase.
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_1_Phase
That means only "Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released". This BZ does not appear to meet Maintenance Support 1 Phase criteria so is being closed WONTFIX. If this is critical for your environment please open a case in the Red Hat Customer Portal, https://access.redhat.com, provide a thorough business justification and ask that the BZ be re-opened for consideration in the next minor release.