[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind

[Sergio Durigan Junior]

On Monday, August 10 2020, Dan Streetman wrote:

> autopkgtest note: nfs-utils(s390x) fails, but appears to have always
> failed; the test runs that 'passed' back in 2017 just skipped the
> now-failing testcase due to lack of machine isolation back then:
> "local-server-client  SKIP Test requires machine-level isolation but testbed does not provide that"
>
> so that autopkgtest failure can be ignored as unrelated to this.

Thanks for the verification, Dan.

I did some investigation regarding this nfs-utils failure on s390x, and
posted my conclusions here:

  https://bugs.launchpad.net/ubuntu/+source/nfs-
utils/+bug/1705483/comments/1

As a follow-up, I filed the following MP for hints-ubuntu-xenial:

  https://code.launchpad.net/~sergiodj/britney/hints-ubuntu-
xenial/+merge/388495

Which should force-badtest the failure.  I'm still waiting on someone to
review and approve the MP.

Thanks,

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

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

Title:
  ypbind not able to socket activate rpcbind under systemd, fails at
  boot unless something else starts rpcbind

Status in nis package in Ubuntu:
  Fix Released
Status in rpcbind package in Ubuntu:
  Fix Released
Status in nis source package in Xenial:
  Invalid
Status in rpcbind source package in Xenial:
  Fix Committed
Status in nis package in Debian:
  Fix Released

Bug description:
  [Impact]

  Due to a missing "WantedBy" directive in the .service file's [Install]
  section, rpcbind does not properly start when the system is booted,
  which can lead to problems if the user needs to mount some NFS
  locations on boot time.

  [Test Case]

  To reproduce the issue, one can do:

  $ lxc launch images:ubuntu/xenial bug1558196-rpcbind --vm
  $ lxc shell bug1558196-rpcbind
  # apt update
  # apt install rpcbind -y
  # systemctl enable rpcbind.service
  # reboot

  After the reboot, you can confirm that the service is not running:

  # systemctl status rpcbind.service
  ● rpcbind.service - RPC bind portmap service
     Loaded: loaded (/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled)
    Drop-In: /run/systemd/generator/rpcbind.service.d
             └─50-rpcbind-$portmap.conf
     Active: inactive (dead)

  [Regression Potential]

  There is virtually no regression potential with this bug, aside from
  the regular "we will rebuild this package against newer versions of
  dependencies, which can introduce unwanted bugs".  The fix is
  extremely simple and self-contained, and just guarantees that the
  package will start normally during boot time.

  [Original Description]

  did apt-get update/upgrade  March 16, 2016
  Description:    Ubuntu Xenial Xerus (development branch)
  Release:        16.04

  rpcbind does not start on boot, tried various systemd debugging steps
  with no clues. After boot systemctl start rpcbind works. There is  a
  /etc/init.d/rpcbind and a /lib/systemd/system/rpcbind.service config
  files which is confusing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1558196/+subscriptions