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:
The service nfs-convert has been enabled by systemd preset (via Bug 1683101).
As package nfs-utils not installed by default. It will stay off even after we just installing the package (the Fedora policy - refs: https://www.freedesktop.org/wiki/Software/systemd/Preset/). But it should become enabled on the next reboot.
However I just realized that even after rebooting this nfs-convert is still in status disabled.
Executing both 'systemctl enable nfs-convert' and 'systemctl preset nfs-convert' can enable it. But why it not being enabled by default? Which is the intention of systemd preset IMHO.
This may not be a real but. But please help check where's the problem. Thanks!
Version-Release number of selected component (if applicable):
systemd-239-45.el8.x86_64
nfs-utils-2.3.3-41.el8.x86_64
redhat-release-8.4-0.5.el8.x86_64
How reproducible:
always
Steps to Reproduce:
1. yum install nfs-utils
2. reboot
3. systemctl is-enabled nfs-convert
Actual results:
[root@kvm-06-guest20 ~]# systemctl status nfs-convert
● nfs-convert.service - Preprocess NFS configuration convertion
Loaded: loaded (/usr/lib/systemd/system/nfs-convert.service; disabled; vendor preset: enabled)
Active: inactive (dead)
[root@kvm-06-guest20 ~]# systemctl is-enabled nfs-convert
disabled
[root@kvm-06-guest20 ~]# grep nfs /usr/lib/systemd/system-preset/90-default.preset
enable nfs-convert.service
[root@kvm-06-guest20 ~]#
[root@kvm-06-guest20 ~]# systemctl cat nfs-convert
# /usr/lib/systemd/system/nfs-convert.service
[Unit]
Description=Preprocess NFS configuration convertion
DefaultDependencies=no
Before=nfs-server.service nfs-mountd.service nfs-idmapd.service
Before=nfs-blkmap.service rpc-statd.service rpc-gssd.service
Before=rpc-statd-notify.service
After=initrd-root-fs.target
ConditionPathExists=/etc/sysconfig/nfs
[Service]
Type=oneshot
ExecStart=/usr/libexec/nfs-utils/nfsconvert.sh
[Install]
RequiredBy=nfs-server.service
RequiredBy=nfs-mountd.service
RequiredBy=nfs-idmapd.service
RequiredBy=nfs-blkmap.service
RequiredBy=rpc-statd.service
RequiredBy=rpc-gssd.service
RequiredBy=rpc-statd-notify.service
[root@kvm-06-guest20 ~]#
[root@kvm-06-guest20 ~]#
[root@kvm-06-guest20 ~]# systemctl preset nfs-convert
Created symlink /etc/systemd/system/nfs-server.service.requires/nfs-convert.service → /usr/lib/systemd/system/nfs-convert.service.
Created symlink /etc/systemd/system/nfs-mountd.service.requires/nfs-convert.service → /usr/lib/systemd/system/nfs-convert.service.
Created symlink /etc/systemd/system/nfs-idmapd.service.requires/nfs-convert.service → /usr/lib/systemd/system/nfs-convert.service.
Created symlink /etc/systemd/system/nfs-blkmap.service.requires/nfs-convert.service → /usr/lib/systemd/system/nfs-convert.service.
Created symlink /etc/systemd/system/rpc-statd.service.requires/nfs-convert.service → /usr/lib/systemd/system/nfs-convert.service.
Created symlink /etc/systemd/system/rpc-gssd.service.requires/nfs-convert.service → /usr/lib/systemd/system/nfs-convert.service.
Created symlink /etc/systemd/system/rpc-statd-notify.service.requires/nfs-convert.service → /usr/lib/systemd/system/nfs-convert.service.
[root@kvm-06-guest20 ~]# echo $?
0
[root@kvm-06-guest20 ~]#
Expected results:
Additional info:
(In reply to Yongcheng Yang from comment #0)
> Description of problem:
>
> The service nfs-convert has been enabled by systemd preset (via Bug 1683101).
> As package nfs-utils not installed by default. It will stay off even after
> we just installing the package (the Fedora policy - refs:
> https://www.freedesktop.org/wiki/Software/systemd/Preset/). But it should
> become enabled on the next reboot.
>
> However I just realized that even after rebooting this nfs-convert is still
> in status disabled.
No. That's not how it works. "systemctl preset" must be called explicitly, just like "systemctl enable".
(In reply to David Tardon from comment #1)
> (In reply to Yongcheng Yang from comment #0)
> > Description of problem:
> >
> > The service nfs-convert has been enabled by systemd preset (via Bug 1683101).
> > As package nfs-utils not installed by default. It will stay off even after
> > we just installing the package (the Fedora policy - refs:
> > https://www.freedesktop.org/wiki/Software/systemd/Preset/). But it should
> > become enabled on the next reboot.
> >
> > However I just realized that even after rebooting this nfs-convert is still
> > in status disabled.
>
> No. That's not how it works. "systemctl preset" must be called explicitly,
> just like "systemctl enable".
... so nfs-utils rpm should be doing it.
Comment 12RHEL Program Management
2021-10-01 07:27:08 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.