[2.4, service-tracking] dhcpd is never started on bionic container in xenial host, and MAAS doesn't show it as failure.

[Andres Rodriguez]

A fresh install of MAAS 2.4 in bionic does not start DHCP after enabled. I installed maas from latest trunk from ppa:maas-maintainers/experimental3:

1. There are no logs whatsoever showing that anything failed. There are simply no logs.
2. No syslog information of why it failed.
3. maas-dhcpd service shows an error, but MAAS doesn't bubble up that at all.

root@bionic:/var/log/maas# sudo service maas-dhcpd status
● maas-dhcpd.service - MAAS instance of ISC DHCP server for IPv4
   Loaded: loaded (/lib/systemd/system/maas-dhcpd.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Tue 2018-01-16 07:15:29 UTC; 10min ago
     Docs: man:dhcpd(8)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/maas-dhcpd.service

Jan 16 07:15:29 bionic systemd[1]: maas-dhcpd.service: Failed to reset devices.list: Operation not permitted
Jan 16 07:15:29 bionic systemd[1]: maas-dhcpd.service: Failed to reset devices.list: Operation not permitted
Jan 16 07:15:29 bionic systemd[1]: maas-dhcpd.service: Failed to reset devices.list: Operation not permitted
Jan 16 07:15:30 bionic systemd[1]: maas-dhcpd.service: Failed to reset devices.list: Operation not permitted
Jan 16 07:15:30 bionic systemd[1]: maas-dhcpd.service: Failed to reset devices.list: Operation not permitted
Jan 16 07:15:30 bionic systemd[1]: maas-dhcpd.service: Failed to reset devices.list: Operation not permitted
Jan 16 07:16:20 bionic systemd[1]: maas-dhcpd.service: Failed to reset devices.list: Operation not permitted
Jan 16 07:16:20 bionic systemd[1]: maas-dhcpd.service: Failed to reset devices.list: Operation not permitted
Jan 16 07:16:21 bionic systemd[1]: maas-dhcpd.service: Failed to reset devices.list: Operation not permitted
Jan 16 07:16:22 bionic systemd[1]: maas-dhcpd.service: Failed to reset devices.list: Operation not permitted

So there's two things to fix:

1. It should show as a failure in MAAS, it currently shows as not started.
2. It shouldn't fail.

[Björn Tillenius (bjornt)]

Tested on an unprivileged bionic container on a xenial host. Everything seems to work for me.

Is maas-dhcp installed on your xenial host? That might be required to setup apparmor correctly.

[Andres Rodriguez (andreserl)]

FWIW, the xenial host was configured following the instructions of [1]. This means I was using a confined container giving some extra permissions.

The *real* issue is that MAAS never reports the failure of starting maas-dhcp as a real failure (on the service tracking).

[1]: https://docs.ubuntu.com/maas/2.3/en/installconfig-lxd-install

[Blake Rouse (blake-rouse)]

I have been trying to reproduce this with latest master that includes https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/342811 which I believe was the actual cause of this issue.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team