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.
Description of problem:
Currently, we're using `systemctl enable` in %post i.e.
/bin/systemctl enable nfs-convert >/dev/null 2>&1 || :
However,
(https://bugzilla.redhat.com/show_bug.cgi?id=1673685#c6)
"the correct way to have this enabled by default is to have it
added to the systemd presets in the `redhat-release` package."
(https://bugzilla.redhat.com/show_bug.cgi?id=1673685#c16)
"The most obvious one in this case is so that we as an organization
can figure out what will be running on your system. The second one is
that scriptlets do not play well with container base image creation,
OSTree image creation and Weldr/Composer. In some of these cases, RPMs
are installed with the --no-scripts flag, so they WILL NOT HAVE THIS
RUNNING. That is why I am telling you that it should either be in the
presets or change the dependency link."
Version-Release number of selected component (if applicable):
nfs-utils-2.3.3-14.el8
How reproducible:
always
Steps to Reproduce:
1. rpm -q nfs-utils --scripts | grep nfs-convert
2.
3.
Actual results:
[root]$ rpm -q nfs-utils --scripts | grep nfs-convert
# Enable nfs-convert so if an old configuration
/bin/systemctl enable nfs-convert >/dev/null 2>&1 || :
[root]$ systemctl is-enabled nfs-convert
enabled
[root]$
Expected results:
No `systemctl enable` in %post while nfs-conver still be enabled
Additional info:
N/A
Should this be open against the `redhat-release` package
since I can not added nfsconvert.service to the presets?
Also, shouldn't the enabling of rpcbind.socket be added
the presets as well?
Comment 2Stephen Gallagher
2019-02-26 16:05:43 UTC
(In reply to Steve Dickson from comment #1)
> Should this be open against the `redhat-release` package
> since I can not added nfsconvert.service to the presets?
>
Stephen help did that, thanks!
However, after this gets fixed we may need to remove
the redundant %post of nfs-utils.spec accordingly.
> Also, shouldn't the enabling of rpcbind.socket be added
> the presets as well?
Looks like we process rpcbind differently of rhel 8 & 7, i.e.
# RHEL-8.0
$ rpm -q rpcbind && rpm -q rpcbind --scripts | grep -E "enable|preset"
rpcbind-1.2.5-3.el8.x86_64
systemctl --no-reload preset rpcbind.service rpcbind.socket &>/dev/null || :
# RHEL-7.6
$ rpm -q rpcbind && rpm -q rpcbind --scripts | grep -E "enable|preset"
rpcbind-0.2.0-47.el7.x86_64
/bin/systemctl enable rpcbind.service >/dev/null 2>&1 || :
Please help decide what we need to change.
(In reply to Yongcheng Yang from comment #3)
> (In reply to Steve Dickson from comment #1)
> > Should this be open against the `redhat-release` package
> > since I can not added nfsconvert.service to the presets?
> >
>
> Stephen help did that, thanks!
>
> However, after this gets fixed we may need to remove
> the redundant %post of nfs-utils.spec accordingly.
Good point... Maybe we should move this bz back to nfs-utils
and open up another redhat-release to add the preset?
>
> > Also, shouldn't the enabling of rpcbind.socket be added
> > the presets as well?
>
> Looks like we process rpcbind differently of rhel 8 & 7, i.e.
>
> # RHEL-8.0
> $ rpm -q rpcbind && rpm -q rpcbind --scripts | grep -E "enable|preset"
> rpcbind-1.2.5-3.el8.x86_64
> systemctl --no-reload preset rpcbind.service rpcbind.socket
> &>/dev/null || :
>
> # RHEL-7.6
> $ rpm -q rpcbind && rpm -q rpcbind --scripts | grep -E "enable|preset"
> rpcbind-0.2.0-47.el7.x86_64
> /bin/systemctl enable rpcbind.service >/dev/null 2>&1 || :
>
> Please help decide what we need to change.
Lets open up another bz against redhat-release to see what
they say...
Boy.. I like opening up bz against other packages!!! ;-)
(In reply to Steve Dickson from comment #4)
> (In reply to Yongcheng Yang from comment #3)
> > However, after this gets fixed we may need to remove
> > the redundant %post of nfs-utils.spec accordingly.
> Good point... Maybe we should move this bz back to nfs-utils
> and open up another redhat-release to add the preset?
>
Just filed another nfs-utils bug 1683895 which depends on this one.
(Not changing this bug's title looks more straightforward IMO)
> >
> > > Also, shouldn't the enabling of rpcbind.socket be added
> > > the presets as well?
> >
> > Looks like we process rpcbind differently of rhel 8 & 7
> > Please help decide what we need to change.
> Lets open up another bz against redhat-release to see what
> they say...
>
Okay, also file bug 1683901 of rhel7
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 (redhat-release 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-2020:4495