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.
Bug 1171603 - Require rpcbind.service in nfs-server.service rather than rpcbind.target
Summary: Require rpcbind.service in nfs-server.service rather than rpcbind.target
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nfs-utils
Version: 7.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Yongcheng Yang
URL:
Whiteboard:
: 1209213 (view as bug list)
Depends On:
Blocks: 1035038 1155425 1172230
TreeView+ depends on / blocked
 
Reported: 2014-12-08 08:27 UTC by Hu Jianwei
Modified: 2019-10-10 09:31 UTC (History)
21 users (show)

Fixed In Version: nfs-utils-1.3.0-0.21.el7
Doc Type: Bug Fix
Doc Text:
Cause: The NFS server systemd scripts did not have the correct rpcbind requirement Consequence: The NFS server failed to come up. Fix: Correct the rpcbind requirement the NFS server systemd scripts Result: The NFS server comes up
Clone Of:
Environment:
Last Closed: 2015-11-19 04:28:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2390771 0 None None None 2016-08-02 08:26:31 UTC
Red Hat Product Errata RHBA-2015:2196 0 normal SHIPPED_LIVE nfs-utils bug fix update 2015-11-19 08:05:04 UTC

Description Hu Jianwei 2014-12-08 08:27:10 UTC 
Description of problem:
Require rpcbind.service in nfs-server.service rather than rpcbind.target

Version-Release number of selected component (if applicable):
nfs-utils-1.3.0-0.4.el7.x86_64
rpcbind-0.2.0-25.el7.x86_64
kernel-3.10.0-201.el7.x86_64
systemd-208-18.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
[root@dhcp-66-83-39 images]# service rpcbind status
Redirecting to /bin/systemctl status  rpcbind.service
rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; static)
   Active: failed (Result: exit-code) since Mon 2014-12-08 16:17:35 CST; 8s ago
 Main PID: 24420 (code=exited, status=2)

Dec 08 16:17:17 dhcp-66-83-39.nay.redhat.com systemd[1]: Starting RPC bind service...
Dec 08 16:17:17 dhcp-66-83-39.nay.redhat.com systemd[1]: Started RPC bind service.
Dec 08 16:17:35 dhcp-66-83-39.nay.redhat.com systemd[1]: Stopping RPC bind service...
Dec 08 16:17:35 dhcp-66-83-39.nay.redhat.com rpcbind[24420]: rpcbind terminating on signal. Restart with "rpcbind -w"
Dec 08 16:17:35 dhcp-66-83-39.nay.redhat.com systemd[1]: rpcbind.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 08 16:17:35 dhcp-66-83-39.nay.redhat.com systemd[1]: Stopped RPC bind service.
Dec 08 16:17:35 dhcp-66-83-39.nay.redhat.com systemd[1]: Unit rpcbind.service entered failed state.
[root@dhcp-66-83-39 images]# 
[root@dhcp-66-83-39 images]# service nfs restart
Redirecting to /bin/systemctl restart  nfs.service
Job for nfs-server.service failed. See 'systemctl status nfs-server.service' and 'journalctl -xn' for details.
[root@dhcp-66-83-39 images]# journalctl -xn
-- Logs begin at Mon 2014-12-08 14:22:49 CST, end at Mon 2014-12-08 16:17:47 CST. --
Dec 08 16:17:47 dhcp-66-83-39.nay.redhat.com systemd[1]: Starting NFS server and services...
-- Subject: Unit nfs-server.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit nfs-server.service has begun starting up.
Dec 08 16:17:47 dhcp-66-83-39.nay.redhat.com kernel: svc: failed to register nfsdv3 RPC service (errno 111).
Dec 08 16:17:47 dhcp-66-83-39.nay.redhat.com kernel: svc: failed to register nfsaclv3 RPC service (errno 111).
Dec 08 16:17:47 dhcp-66-83-39.nay.redhat.com rpc.nfsd[24554]: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
Dec 08 16:17:47 dhcp-66-83-39.nay.redhat.com kernel: svc: failed to register nfsdv3 RPC service (errno 97).
Dec 08 16:17:47 dhcp-66-83-39.nay.redhat.com kernel: svc: failed to register nfsaclv3 RPC service (errno 97).
Dec 08 16:17:47 dhcp-66-83-39.nay.redhat.com rpc.nfsd[24554]: rpc.nfsd: unable to set any sockets for nfsd
Dec 08 16:17:47 dhcp-66-83-39.nay.redhat.com systemd[1]: nfs-server.service: main process exited, code=exited, status=1/FAILURE
Dec 08 16:17:47 dhcp-66-83-39.nay.redhat.com systemd[1]: Failed to start NFS server and services.
-- Subject: Unit nfs-server.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit nfs-server.service has failed.
-- 
-- The result is failed.
Dec 08 16:17:47 dhcp-66-83-39.nay.redhat.com systemd[1]: Unit nfs-server.service entered failed state.


Actual results:
As above steps, the NFS service fails to start unless the rpcbind.service in  /lib/systemd/system/nfs-server.service, not rpcbind.target


Expected results:
After change to rpcbind.service, the nfs can be started normally.
[root@dhcp-66-83-39 images]# cat /usr/lib/systemd/system/nfs-server.service
[Unit]
Description=NFS server and services
Requires= network.target proc-fs-nfsd.mount rpcbind.service
Requires= nfs-mountd.service
Wants=rpc-statd.service nfs-idmapd.service
Wants=rpc-statd-notify.service

...

[root@dhcp-66-83-39 images]# service rpcbind status
Redirecting to /bin/systemctl status  rpcbind.service
rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; static)
   Active: failed (Result: exit-code) since Mon 2014-12-08 16:17:35 CST; 3min 10s ago
 Main PID: 24420 (code=exited, status=2)
   CGroup: /system.slice/rpcbind.service

Dec 08 16:17:17 dhcp-66-83-39.nay.redhat.com systemd[1]: Starting RPC bind service...
Dec 08 16:17:17 dhcp-66-83-39.nay.redhat.com systemd[1]: Started RPC bind service.
Dec 08 16:17:35 dhcp-66-83-39.nay.redhat.com systemd[1]: Stopping RPC bind service...
Dec 08 16:17:35 dhcp-66-83-39.nay.redhat.com rpcbind[24420]: rpcbind terminating on signal. Restart with "rpcbind -w"
Dec 08 16:17:35 dhcp-66-83-39.nay.redhat.com systemd[1]: rpcbind.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 08 16:17:35 dhcp-66-83-39.nay.redhat.com systemd[1]: Stopped RPC bind service.
Dec 08 16:17:35 dhcp-66-83-39.nay.redhat.com systemd[1]: Unit rpcbind.service entered failed state.

[root@dhcp-66-83-39 images]# systemctl daemon-reload
[root@dhcp-66-83-39 images]# service nfs restart
Redirecting to /bin/systemctl restart  nfs.service

[root@dhcp-66-83-39 images]# service rpcbind status
Redirecting to /bin/systemctl status  rpcbind.service
rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; static)
   Active: active (running) since Mon 2014-12-08 16:20:57 CST; 4s ago
  Process: 24647 ExecStart=/sbin/rpcbind -w ${RPCBIND_ARGS} (code=exited, status=0/SUCCESS)
 Main PID: 24649 (rpcbind)
   CGroup: /system.slice/rpcbind.service
           └─24649 /sbin/rpcbind -w

Dec 08 16:20:57 dhcp-66-83-39.nay.redhat.com systemd[1]: Started RPC bind service.
[root@dhcp-66-83-39 images]# 
[root@dhcp-66-83-39 images]# service nfs status
Redirecting to /bin/systemctl status  nfs.service
nfs-server.service - NFS server and services
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; disabled)
   Active: active (exited) since Mon 2014-12-08 16:20:57 CST; 1min 35s ago
  Process: 24654 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=0/SUCCESS)
  Process: 24652 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
 Main PID: 24654 (code=exited, status=0/SUCCESS)

Dec 08 16:20:57 dhcp-66-83-39.nay.redhat.com systemd[1]: Starting NFS server and services...
Dec 08 16:20:57 dhcp-66-83-39.nay.redhat.com systemd[1]: Started NFS server and services.

Additional info:
Bug 768550 - /lib/systemd/system/nfs-server.service does not reference dependency on rpcbind

But on some machine, I can not stop the rpcbind service

[root@ibm-x3650m3-08 SOURCES]# rpm -q kernel systemd nfs-utils rpcbind
kernel-3.10.0-201.el7.x86_64
systemd-208-18.el7.x86_64
nfs-utils-1.3.0-0.4.el7.x86_64
rpcbind-0.2.0-25.el7.x86_64

[root@ibm-x3650m3-08 SOURCES]# service rpcbind stop
Redirecting to /bin/systemctl stop  rpcbind.service
Job for rpcbind.service canceled.

[root@ibm-x3650m3-08 SOURCES]# service rpcbind status
Redirecting to /bin/systemctl status  rpcbind.service
rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; static)
   Active: active (running) since Mon 2014-12-08 16:23:40 CST; 5s ago
  Process: 28784 ExecStart=/sbin/rpcbind -w ${RPCBIND_ARGS} (code=exited, status=0/SUCCESS)
 Main PID: 28785 (rpcbind)
   CGroup: /system.slice/rpcbind.service
           └─28785 /sbin/rpcbind -w

Dec 08 16:23:40 ibm-x3650m3-08.qe.lab.eng.nay.redhat.com systemd[1]: Started RPC bind service.
Comment 3 Dennis Jacobfeuerborn 2015-06-18 17:59:32 UTC 
I ran into a similar Problem and was about to file a bug and then found this one.

For me the nfs-server.service startup succeeds but only after a 60 seconds delay.
This is what appears in the logs:

Jun 18 19:00:58 test systemd: Starting NFS Mount Daemon...
...
Jun 18 19:01:58 test rpc.mountd[2021]: Failed to unregister program
100005, version 1

I noticed that this delay does not occur when I manually start rpcbind.service first.

With the above information I copied nfs-server.service to /etc/systemd/system and replaced the two occurrences of rpcbind.target with rpcbind.service.
After that the delay when starting nfs-server.service is gone and I no longer see any failures in the log.
Comment 4 Steve Dickson 2015-06-26 14:59:48 UTC 
*** Bug 1203765 has been marked as a duplicate of this bug. ***
Comment 7 Dennis Jacobfeuerborn 2015-08-03 15:01:23 UTC 
FYI in order to really fix this in a pacemaker cluster context I had to also modify the nfs-lock.service and rpc-statd.service files in order to get rid of the delay problem.
Comment 8 Andrew J. Schorr 2015-08-04 12:39:21 UTC 
And rpc-rquotad.service also requires rpcbind.target.  Should that also be changed?
Comment 9 Steve Dickson 2015-08-05 15:09:44 UTC 
(In reply to Andrew J. Schorr from comment #8)
> And rpc-rquotad.service also requires rpcbind.target.  Should that also be
> changed?
Note, rpc-rquotad.service is no longer part of nfs-utils package
it was moved to the qouta package.
Comment 10 Steve Dickson 2015-08-05 15:11:37 UTC 
(In reply to Dennis Jacobfeuerborn from comment #7)
> FYI in order to really fix this in a pacemaker cluster context I had to also
> modify the nfs-lock.service and rpc-statd.service files in order to get rid
> of the delay problem.

Why and how? Please open another bz if needed... This one is done! ;-)
Comment 11 Dennis Jacobfeuerborn 2015-08-05 16:53:03 UTC 
So what was the actual fix in this case? While while changing rpcbind.target to rpcbind.service makes things work it doesn't look like an appropriate fix. The question is what is rpcbind.target supposed to accomplish? If its inclusion was a mistake then the target itself and all its references would need to be removed for a proper fix but if it is still used for some reason than all references still need to checked to see if they are correct or need to be changed.

In summary I don't think this bug is properly fixed yet if only the reference in nfs-server.service was changed.
Comment 12 Todd Vierling 2015-09-11 18:30:38 UTC 
Looking in beta package nfs-utils-1.3.0-0.17.el7, yes, only nfs-server.service was changed so far. In that package alone, rpc-statd.service also needs this change as it still reads:

systemd/rpc-statd.service:Requires=nss-lookup.target rpcbind.target
systemd/rpc-statd.service:After=network.target nss-lookup.target rpcbind.target

My user definitely will need a fix in rpc-statd.service as well, as that's the daemon having trouble in their case. Manually editing rpc-statd.service to change rpcbind.target to rpcbind.service works.

The correct fix is to fix all these references, as they are all incorrect. There exists no rpcbind.target anywhere; it's only named rpcbind.service.

(Other bugs may need to be opened to fix this elsewhere, e.g. in the quota package's rpc-rquotad.service which was noted as broken above.)
Comment 13 Yongcheng Yang 2015-09-12 05:21:46 UTC 
(In reply to Todd Vierling from comment #12)
> Looking in beta package nfs-utils-1.3.0-0.17.el7, yes, only
> nfs-server.service was changed so far. In that package alone,
> rpc-statd.service also needs this change as it still reads:
> 
> systemd/rpc-statd.service:Requires=nss-lookup.target rpcbind.target
> systemd/rpc-statd.service:After=network.target nss-lookup.target
> rpcbind.target
> 
Hi Todd,
Maybe it's better to open another bug for rpc-statd.service (or nfs-lock.service) according to Comment 10.
Then we can trace the issue easier on it. Thanks.

> My user definitely will need a fix in rpc-statd.service as well, as that's
> the daemon having trouble in their case. Manually editing rpc-statd.service
> to change rpcbind.target to rpcbind.service works.
> 
And please help to provide the user reproducer.
I can't trigger the rpc-statd.service issue using the Description's steps.
It seems has no difference using "rpcbind.service" or "rpcbind.target".

[root@hp-dl580g7-03 ~]# cat /usr/lib/systemd/system/rpc-statd.service | grep rpcbind
Requires=nss-lookup.target rpcbind.target
After=network.target nss-lookup.target rpcbind.target
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ using rpcbind.target
[root@hp-dl580g7-03 ~]# systemctl daemon-reload
[root@hp-dl580g7-03 ~]# service rpcbind stop; service rpcbind stop
Redirecting to /bin/systemctl stop  rpcbind.service
Warning: Stopping rpcbind.service, but it can still be activated by:
  rpcbind.socket
Redirecting to /bin/systemctl stop  rpcbind.service
Warning: Stopping rpcbind.service, but it can still be activated by:
  rpcbind.socket
[root@hp-dl580g7-03 ~]# service rpcbind status
Redirecting to /bin/systemctl status  rpcbind.service
● rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled)
   Active: inactive (dead) since Sat 2015-09-12 13:07:59 CST; 5s ago
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ stop the rpcbind.service
 Main PID: 13180 (code=exited, status=0/SUCCESS)

Sep 12 13:06:53 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Starting RPC bind service...
Sep 12 13:06:53 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Started RPC bind service.
Sep 12 13:07:59 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Stopping RPC bind service...
Sep 12 13:07:59 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Stopped RPC bind service.
Sep 12 13:07:59 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Stopped RPC bind service.
[root@hp-dl580g7-03 ~]# service rpc-statd restart; service rpc-statd status
Redirecting to /bin/systemctl restart  rpc-statd.service
Redirecting to /bin/systemctl status  rpc-statd.service
● rpc-statd.service - NFS status monitor for NFSv2/3 locking.
   Loaded: loaded (/usr/lib/systemd/system/rpc-statd.service; static; vendor preset: disabled)
   Active: active (running) since Sat 2015-09-12 13:08:25 CST; 26ms ago
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ start rpc-statd successfully
  Process: 13274 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=0/SUCCESS)
 Main PID: 13275 (rpc.statd)
   CGroup: /system.slice/rpc-statd.service
           └─13275 /usr/sbin/rpc.statd --no-notify

Sep 12 13:08:25 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Starting NFS status monitor for NFSv2/3 loc.....
Sep 12 13:08:25 hp-dl580g7-03.rhts.eng.nay.redhat.com rpc.statd[13275]: Version 1.3.0 starting
Sep 12 13:08:25 hp-dl580g7-03.rhts.eng.nay.redhat.com rpc.statd[13275]: Flags: TI-RPC
Sep 12 13:08:25 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Started NFS status monitor for NFSv2/3 locking..
Hint: Some lines were ellipsized, use -l to show in full.
[root@hp-dl580g7-03 ~]# 

[root@hp-dl580g7-03 system]# cat rpc-statd.service | grep rpcbind
Requires=nss-lookup.target rpcbind.service
After=network.target nss-lookup.target rpcbind.service
[root@hp-dl580g7-03 system]# systemctl daemon-reload
[root@hp-dl580g7-03 system]# service rpcbind stop; service rpcbind stop
Redirecting to /bin/systemctl stop  rpcbind.service
Warning: Stopping rpcbind.service, but it can still be activated by:
  rpcbind.socket
Redirecting to /bin/systemctl stop  rpcbind.service
Warning: Stopping rpcbind.service, but it can still be activated by:
  rpcbind.socket
[root@hp-dl580g7-03 system]# service rpcbind status
Redirecting to /bin/systemctl status  rpcbind.service
● rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled)
   Active: inactive (dead) since Sat 2015-09-12 13:06:41 CST; 5s ago
 Main PID: 13084 (code=exited, status=0/SUCCESS)

Sep 12 13:03:31 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Starting RPC bind service...
Sep 12 13:03:31 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Started RPC bind service.
Sep 12 13:06:41 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Stopping RPC bind service...
Sep 12 13:06:41 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Stopped RPC bind service.
Sep 12 13:06:41 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Stopped RPC bind service.
[root@hp-dl580g7-03 system]# service rpc-statd restart
Redirecting to /bin/systemctl restart  rpc-statd.service
[root@hp-dl580g7-03 system]# service rpc-statd status
Redirecting to /bin/systemctl status  rpc-statd.service
● rpc-statd.service - NFS status monitor for NFSv2/3 locking.
   Loaded: loaded (/usr/lib/systemd/system/rpc-statd.service; static; vendor preset: disabled)
   Active: active (running) since Sat 2015-09-12 13:06:54 CST; 3s ago
  Process: 13181 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=0/SUCCESS)
 Main PID: 13182 (rpc.statd)
   CGroup: /system.slice/rpc-statd.service
           └─13182 /usr/sbin/rpc.statd --no-notify

Sep 12 13:06:53 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
Sep 12 13:06:53 hp-dl580g7-03.rhts.eng.nay.redhat.com rpc.statd[13182]: Version 1.3.0 starting
Sep 12 13:06:53 hp-dl580g7-03.rhts.eng.nay.redhat.com rpc.statd[13182]: Flags: TI-RPC
Sep 12 13:06:54 hp-dl580g7-03.rhts.eng.nay.redhat.com systemd[1]: Started NFS status monitor for NFSv2/3 locking..
[root@hp-dl580g7-03 system]#
Comment 15 Todd Vierling 2015-09-12 18:31:35 UTC 
(In reply to Yongcheng Yang from comment #13)
> (In reply to Todd Vierling from comment #12)
> > Looking in beta package nfs-utils-1.3.0-0.17.el7, yes, only
> > nfs-server.service was changed so far. In that package alone,
> > rpc-statd.service also needs this change as it still reads:
> > 
> > systemd/rpc-statd.service:Requires=nss-lookup.target rpcbind.target
> > systemd/rpc-statd.service:After=network.target nss-lookup.target
> > rpcbind.target
> > 
> Hi Todd,
> Maybe it's better to open another bug for rpc-statd.service (or
> nfs-lock.service) according to Comment 10.
> Then we can trace the issue easier on it. Thanks.

...Huh? Did I stutter?

It's the same package and the same issue and the same fix, just a different file. This bug is only half-fixed as of this writing.

===

> > My user definitely will need a fix in rpc-statd.service as well, as that's
> > the daemon having trouble in their case. Manually editing rpc-statd.service
> > to change rpcbind.target to rpcbind.service works.
> > 
> And please help to provide the user reproducer.

I can't provide access to their systems, but why is a reliable reproducer needed? Simple logic can explain why it's still a bug in rpc-statd.service: there is *no* rpcbind.target anywhere in the systemd configuration, but rpc-statd.service is depending on it. This is an obvious bug.

How is this so difficult to understand? It's two tiny tweaks that are dead simple: change "rpcbind.target", which doesn't exist, to "rpcbind.service", which does exist, on two lines of rpc-statd.service.

===

> I can't trigger the rpc-statd.service issue using the Description's steps.
> It seems has no difference using "rpcbind.service" or "rpcbind.target".

systemd by its nature starts up services in parallel, and because of that, reproducers for dependency errors are often difficult to come by. It's a race condition.

The whole point is that systemd *requires working dependencies*. "rpcbind.target" is not a working dependency because that target doesn't exist.

This is NOT rocket science. It's a typo with a known fix. Just fix it.
Comment 16 Todd Vierling 2015-09-12 18:38:39 UTC 
Hell, just call up Lennart and ask. He will tell you the same thing, this is an obvious typo in rpc-statd.service, and no reproducer is needed.
Comment 22 errata-xmlrpc 2015-11-19 04:28:33 UTC 
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, 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://rhn.redhat.com/errata/RHBA-2015-2196.html
Comment 23 Yongcheng Yang 2016-02-14 08:02:11 UTC 
*** Bug 1209213 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.