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

Bug #1743515 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Expired
High
Unassigned

Bug Description

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.

Revision history for this message
Andres Rodriguez (andreserl) wrote : Re: [2.4, trunk 6518-gca32acf] dhcpd is never started on bionic container in xenial host, and MAAS doesn't show it as failure.
summary: [2.4, trunk 6518-gca32acf] dhcpd is never started on bionic container in
- xenial host, when it should show a failure
+ xenial host, and MAAS doesn't show it as failure.
description: updated
Changed in maas:
milestone: none → 2.4.0alpha1
importance: Undecided → Critical
status: New → Triaged
Revision history for this message
Björn Tillenius (bjornt) wrote :

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.

Changed in maas:
status: Triaged → Incomplete
Revision history for this message
Andres Rodriguez (andreserl) wrote :

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

Changed in maas:
status: Incomplete → Triaged
Changed in maas:
milestone: 2.4.0alpha1 → 2.4.0alpha2
Changed in maas:
milestone: 2.4.0alpha2 → 2.4.0beta1
summary: - [2.4, trunk 6518-gca32acf] dhcpd is never started on bionic container in
+ [2.4, service-tracking] dhcpd is never started on bionic container in
xenial host, and MAAS doesn't show it as failure.
Changed in maas:
importance: Critical → High
Changed in maas:
milestone: 2.4.0beta1 → 2.4.0beta2
Revision history for this message
Blake Rouse (blake-rouse) wrote :

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.

Changed in maas:
status: Triaged → Incomplete
Changed in maas:
milestone: 2.4.0beta2 → 2.4.0rc1
Changed in maas:
milestone: 2.4.0rc1 → 2.4.0rc2
Revision history for this message
Adam Collard (adam-collard) wrote :

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

Changed in maas:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.