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.
Opening this as a systemd bug, though it's possible the problem is elsewhere. When I first boot my machine, my nfs-secure.service is disabled:
# systemctl status nfs-secure.service
nfs-secure.service - Secure NFS
Loaded: loaded (/usr/lib/systemd/system/nfs-secure.service; disabled)
Active: inactive (dead)
...I then try to enable it and get this cryptic error:
# systemctl enable nfs-secure.service
Failed to issue method call: Unit nfs-secure.service is not loaded.
...I can however start it without any issue:
# systemctl start nfs-secure.service
# systemctl status nfs-secure.service
nfs-secure.service - Secure NFS
Loaded: loaded (/usr/lib/systemd/system/nfs-secure.service; disabled)
Active: active (running) since Fri 2014-02-14 10:29:19 EST; 19s ago
Process: 1981 ExecStart=/usr/sbin/rpc.gssd $RPCGSSDARGS (code=exited, status=0/SUCCESS)
Main PID: 1982 (rpc.gssd)
CGroup: /system.slice/nfs-secure.service
└─1982 /usr/sbin/rpc.gssd
Feb 14 10:29:19 rhel7.example.com systemd[1]: Started Secure NFS.
...and once I do, then I can enable it:
# systemctl enable nfs-secure.service
ln -s '/usr/lib/systemd/system/nfs-secure.service' '/etc/systemd/system/nfs.target.wants/nfs-secure.service'
...is it really not possible to enable a service without starting it first, or is this a bug?
Host was yum updated this morning, so package versions should be the latest as of today:
# rpm -qa systemd\* nfs-utils
systemd-devel-208-2.el7.x86_64
systemd-208-2.el7.x86_64
systemd-sysv-208-2.el7.x86_64
nfs-utils-1.2.9-4.el7.x86_64
systemd-libs-208-2.el7.x86_64
Opening this as a systemd bug, though it's possible the problem is elsewhere. When I first boot my machine, my nfs-secure.service is disabled: # systemctl status nfs-secure.service nfs-secure.service - Secure NFS Loaded: loaded (/usr/lib/systemd/system/nfs-secure.service; disabled) Active: inactive (dead) ...I then try to enable it and get this cryptic error: # systemctl enable nfs-secure.service Failed to issue method call: Unit nfs-secure.service is not loaded. ...I can however start it without any issue: # systemctl start nfs-secure.service # systemctl status nfs-secure.service nfs-secure.service - Secure NFS Loaded: loaded (/usr/lib/systemd/system/nfs-secure.service; disabled) Active: active (running) since Fri 2014-02-14 10:29:19 EST; 19s ago Process: 1981 ExecStart=/usr/sbin/rpc.gssd $RPCGSSDARGS (code=exited, status=0/SUCCESS) Main PID: 1982 (rpc.gssd) CGroup: /system.slice/nfs-secure.service └─1982 /usr/sbin/rpc.gssd Feb 14 10:29:19 rhel7.example.com systemd[1]: Started Secure NFS. ...and once I do, then I can enable it: # systemctl enable nfs-secure.service ln -s '/usr/lib/systemd/system/nfs-secure.service' '/etc/systemd/system/nfs.target.wants/nfs-secure.service' ...is it really not possible to enable a service without starting it first, or is this a bug? Host was yum updated this morning, so package versions should be the latest as of today: # rpm -qa systemd\* nfs-utils systemd-devel-208-2.el7.x86_64 systemd-208-2.el7.x86_64 systemd-sysv-208-2.el7.x86_64 nfs-utils-1.2.9-4.el7.x86_64 systemd-libs-208-2.el7.x86_64