Description of problem:
The nfs-utils-1.3.1-5.0.fc21 systemd service files in /usr/lib/systemd/system are incorrectly requiring rpcbind.target instead of rpcbind.service. As described in "man:systemd.special" the rpcbind.target is a "special passive system unit" and should only have an "After=rpcbind.target" line for services that "consume" the services of rpcbind. Having a "Requires=rpcbind.target" might be appropriate only in the file /usr/lib/systemd/system/rpcbind.service ("Wants=" is recommended instead of "Requires=" for the service that "pulls in" a passive target).

The nfs-utils systemd services that use RPC should have either "Requires=rpcbind.service" if RPC is mandatory or "Wants=rpcbind.service" if RPC is optional, and either "After=rpcbind.service" or "After=rpcbind.target". [R]pcbind.service currently does not "pull in" rpcbind.target as it should (see Bug 1183970) so "After=rpcbind.service" is preferable to "After=rpcbind.target" until that is fixed (and maybe even then).

The nfs-utils systemd services that use other passive targets (e.g. nss-lookup.target) have the same problem as with rpcbind.target. Terminal commands and output follow.

###############################################################################
[root@archer ~]# rpm -q nfs-utils rpcbind systemd
nfs-utils-1.3.1-5.0.fc21.x86_64
rpcbind-0.2.2-1.1.fc21.x86_64
systemd-216-14.fc21.x86_64
###############################################################################
[root@archer ~]# grep rpcbind $(rpm -ql nfs-utils | grep /usr/lib/systemd/system) | grep -v 'wants$'
/usr/lib/systemd/system/nfs-lock.service:Requires=nss-lookup.target rpcbind.target
/usr/lib/systemd/system/nfs-lock.service:After=network.target nss-lookup.target rpcbind.target
/usr/lib/systemd/system/nfs-server.service:Requires= network.target proc-fs-nfsd.mount rpcbind.target
/usr/lib/systemd/system/nfs-server.service:After= network.target proc-fs-nfsd.mount rpcbind.target nfs-mountd.service
/usr/lib/systemd/system/nfs.service:Requires= network.target proc-fs-nfsd.mount rpcbind.target
/usr/lib/systemd/system/nfs.service:After= network.target proc-fs-nfsd.mount rpcbind.target nfs-mountd.service
grep: /usr/lib/systemd/system/nfs.target.wants: Is a directory
/usr/lib/systemd/system/rpc-statd.service:Requires=nss-lookup.target rpcbind.target
/usr/lib/systemd/system/rpc-statd.service:After=network.target nss-lookup.target rpcbind.target
###############################################################################
[root@archer ~]# man -P cat systemd.special | grep -A4 'SPECIAL PASSIVE SYSTEM UNITS' | sed 's/^ *//'
SPECIAL PASSIVE SYSTEM UNITS
A number of special system targets are defined that can be used to properly order boot-up of optional services. These targets are generally not part of the initial boot transaction,
unless they are explicitly pulled in by one of the implementing services. Note specifically that these passive target units are generally not pulled in by the consumer of a service, but
by the provider of the service. This means: a consuming service should order itself after these targets (as appropriate), but not pull it in. A providing service should order itself
before these targets (as appropriate) and pull it in (via a Wants= type dependency).
###############################################################################
[root@archer ~]# man -P cat systemd.special | grep -C1 portmapper | sed 's/^ *//'
rpcbind.target
The portmapper/rpcbind pulls in this target and orders itself before it, to indicate its availability. systemd automatically adds dependencies of type After= for this target unit to
all SysV init script service units with an LSB header referring to the "$portmap" facility.