Commit got into master branch upstream:

commit 907426b00bdcd69d9a56ac1870990e8ae8c6fe9f
Author: Rafael David Tinoco <rafael.tin...@canonical.com>
Date:   Wed Feb 15 10:26:55 2017 -0500

    systemd: Fix nfs-mountd dependency on rpcbind

    Following commit 91da135f - it replaced "rpcbind.target" by 
"rpcbind.socket" in
    some unit files - "rpcbind.socket" should also be added to 
"nfs-mountd.service"
    as a dependency to avoid race conditions.

    Usually "rpcbind.socket" is either started as a "sockets.target" 
dependency, or
    as a dependency for "nfs-server.service", when unit files include it in
    "BindsTo" or "After". Unfortunately there is a possilibility to have
    "nfs-mountd.service" started when the rpcbind socket is not yet created:

    systemd[1]: Starting NFS Mount Daemon...
    systemd[1]: nfs-mountd.service: Control process exited, code=exited status=1
    systemd[1]: Failed to start NFS Mount Daemon.
    systemd[1]: nfs-mountd.service: Unit entered failed state.
    systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.

    Nowadays "nfs-mountd.service" uses "BindTo" directive to 
"nfs-server.service".
    That, per se, doesn't guarantee ordering for NFS server to start rpcbind 
and for
    nfs-mountd to depend on it.

    https://bugs.launchpad.net/bugs/1590799

    Reviewed-by: NeilBrown <ne...@suse.com>
    Signed-off-by: Rafael David Tinoco <rafael.tin...@canonical.com>
    Signed-off-by: Steve Dickson <ste...@redhat.com>

Now I can do the SRU and provide the fix proposal.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590799

Title:
  nfs-kernel-server does not start because of dependency failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to