Comment 3 for bug 1452644

There is something weird going on, since every boot behaves a bit differently:

[ 44.264445] systemd[1]: Found ordering cycle on nfs-server.service/start
[ 44.264447] systemd[1]: Found dependency on nfs-mountd.service/start
[ 44.264448] systemd[1]: Found dependency on network.target/start
[ 44.264449] systemd[1]: Found dependency on NetworkManager.service/start
[ 44.264450] systemd[1]: Found dependency on basic.target/start
[ 44.264451] systemd[1]: Found dependency on sockets.target/start
[ 44.264452] systemd[1]: Found dependency on acpid.socket/start
[ 44.264453] systemd[1]: Found dependency on sysinit.target/start
[ 44.264455] systemd[1]: Found dependency on setserial.service/start
[ 44.264457] systemd[1]: Found dependency on remote-fs.target/start
[ 44.264460] systemd[1]: Found dependency on remote-fs-pre.target/start
[ 44.264461] systemd[1]: Found dependency on nfs-server.service/start
[ 44.264462] systemd[1]: Breaking ordering cycle by deleting job nfs-mountd.service/start
[ 44.264463] systemd[1]: Job nfs-mountd.service/start deleted to break ordering cycle starting with nfs-server.service/start

This time NFS is not working.

rpcinfo
   program version netid address service owner
    100000 4 tcp6 ::.0.111 portmapper superuser
    100000 3 tcp6 ::.0.111 portmapper superuser
    100000 4 udp6 ::.0.111 portmapper superuser
    100000 3 udp6 ::.0.111 portmapper superuser
    100000 4 tcp 0.0.0.0.0.111 portmapper superuser
    100000 3 tcp 0.0.0.0.0.111 portmapper superuser
    100000 2 tcp 0.0.0.0.0.111 portmapper superuser
    100000 4 udp 0.0.0.0.0.111 portmapper superuser
    100000 3 udp 0.0.0.0.0.111 portmapper superuser
    100000 2 udp 0.0.0.0.0.111 portmapper superuser
    100000 4 local /run/rpcbind.sock portmapper superuser
    100000 3 local /run/rpcbind.sock portmapper superuser

But sudo systemctl start nfs-kernel-server
starts nfs server beautifully