[Bug 1614248] [NEW] Package autofs does not include autofs.service file

[Maciej Puzio]

Public bug reported:

Package autofs in Ubuntu 16.04 includes SysV startup script
(/etc/init.d/autofs) and Upstart unit (/etc/init/autofs.conf), but does
not include systemd service file. As a result, systemd starts autofs as
part of its LSB (sysv) processing, which makes it difficult to ensure
that autofs is started after services that it requires for proper
functioning. In particular, unit autogenerated by systemd-sysv-generator
for autofs does not include dependency on sssd.service.

It appears that on the installation that I tested, systemd starts LSB
services well after sssd is started, so the issue does not cause any
visible problems, but this startup sequence is accidental. Given the
number of other issues related to autofs startup in Xenial, requiring
users to get their hands dirty just to have autofs run properly after
boot, I think it would be advantageous to fix this simple oversight.
(See bug 1566508, bug 1584818, bug 1588915)

I attach an example service file for autofs that fixes this problem. In
addition to sssd.service, this unit could also list nslcd.service,
slapd.service and ypbind.service/nis.service in its After= line.
However, these service files are also missing from their respective
packages, and I am not even sure how NIS client service file would be
called.

$lsb_release -rd
Description:    Ubuntu 16.04.1 LTS
Release:        16.04

$apt-cache policy autofs
autofs:
  Installed: 5.1.1-1ubuntu3
  Candidate: 5.1.1-1ubuntu3

** Affects: autofs (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "autofs.service"
   https://bugs.launchpad.net/bugs/1614248/+attachment/4722917/+files/autofs.service

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

Title:
  Package autofs does not include autofs.service file

Status in autofs package in Ubuntu:
  New

Bug description:
  Package autofs in Ubuntu 16.04 includes SysV startup script
  (/etc/init.d/autofs) and Upstart unit (/etc/init/autofs.conf), but
  does not include systemd service file. As a result, systemd starts
  autofs as part of its LSB (sysv) processing, which makes it difficult
  to ensure that autofs is started after services that it requires for
  proper functioning. In particular, unit autogenerated by systemd-sysv-
  generator for autofs does not include dependency on sssd.service.

  It appears that on the installation that I tested, systemd starts LSB
  services well after sssd is started, so the issue does not cause any
  visible problems, but this startup sequence is accidental. Given the
  number of other issues related to autofs startup in Xenial, requiring
  users to get their hands dirty just to have autofs run properly after
  boot, I think it would be advantageous to fix this simple oversight.
  (See bug 1566508, bug 1584818, bug 1588915)

  I attach an example service file for autofs that fixes this problem.
  In addition to sssd.service, this unit could also list nslcd.service,
  slapd.service and ypbind.service/nis.service in its After= line.
  However, these service files are also missing from their respective
  packages, and I am not even sure how NIS client service file would be
  called.

  $lsb_release -rd
  Description:    Ubuntu 16.04.1 LTS
  Release:        16.04

  $apt-cache policy autofs
  autofs:
    Installed: 5.1.1-1ubuntu3
    Candidate: 5.1.1-1ubuntu3

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