[Bug 1557015] Re: idmapd not started by systemd on nfs clients (xenial beta1)

Steve Langasek steve.langasek at canonical.com
Mon Mar 14 20:55:21 UTC 2016


This is entirely by design. Per upstream, idmapd is not needed on
current systems; it is superseded by the kernel upcall interface,
configured via /etc/request-key.d/id_resolver.conf to use
/usr/sbin/nfsidmap.  Please explain why you believe this is not working.

** Changed in: nfs-utils (Ubuntu)
       Status: New => Incomplete

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

Title:
  idmapd not started by systemd on nfs clients (xenial beta1)

Status in nfs-utils package in Ubuntu:
  Incomplete

Bug description:
  rpc.idmapd is not started on clients, but it should, especially if
  explicitly enabled in /etc/default/nfs-common. The corresponding
  systemd service appears as masked and its file
  (/lib/systemd/system/idmapd.service) is linked to /dev/null.

  This is a regression from the previous LTS version 14.04 and prevents
  NFSv4 users from upgrading.

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



More information about the foundations-bugs mailing list