MAAS dhcp fails to start on up-to-date Xenial with MAAS built from source
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Critical
|
Unassigned | ||
isc-dhcp (Ubuntu) |
Fix Released
|
Critical
|
LaMont Jones |
Bug Description
/var/log/kern.log
Jan 25 03:54:41 autopkgtest kernel: [ 598.488307] audit: type=1400 audit(145371208
/var/log/syslog
Jan 25 05:21:37 autopkgtest systemd[1]: Starting MAAS instance of ISC DHCP server for IPv4...
Jan 25 05:21:37 autopkgtest systemd[1]: Started MAAS instance of ISC DHCP server for IPv4.
Jan 25 05:21:37 autopkgtest dhcpd[17722]: Can't chown new lease file: Operation not permitted
Jan 25 05:21:37 autopkgtest dhcpd[17722]:
Jan 25 05:21:37 autopkgtest dhcpd[17722]: If you think you have received this message due to a bug rather
Jan 25 05:21:37 autopkgtest dhcpd[17722]: than a configuration issue please read the section on submitting
Jan 25 05:21:37 autopkgtest dhcpd[17722]: bugs on either our web page at www.isc.org or in the README file
Jan 25 05:21:37 autopkgtest dhcpd[17722]: before submitting a bug. These pages explain the proper
Jan 25 05:21:37 autopkgtest dhcpd[17722]: process and the information we find helpful for debugging..
Jan 25 05:21:37 autopkgtest dhcpd[17722]:
Jan 25 05:21:37 autopkgtest dhcpd[17722]: exiting.
Jan 25 05:21:37 autopkgtest systemd[1]: maas-dhcpd.service: Main process exited, code=exited, status=1/FAILURE
Jan 25 05:21:37 autopkgtest systemd[1]: maas-dhcpd.service: Unit entered failed state.
Jan 25 05:21:37 autopkgtest systemd[1]: maas-dhcpd.service: Failed with result 'exit-code'.
root@autopkgtest:~# ls -l /var/lib/
-rw-r--r-- 1 maas maas 0 Jan 25 03:54 /var/lib/
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in isc-dhcp (Ubuntu): | |
milestone: | none → trusty-updates |
milestone: | trusty-updates → ubuntu-16.04 |
milestone: | ubuntu-16.04 → trusty-updates |
milestone: | trusty-updates → ubuntu-16.04 |
Changed in isc-dhcp (Ubuntu Trusty): | |
milestone: | none → trusty-updates |
no longer affects: | isc-dhcp (Ubuntu Trusty) |
Sorry. Precocious submit.
The machine is the CI environment. It's installed from a Xenial image that's fully updated and MAAS is built from source. Even though maas owns the lease file, there seems to be an issue with its ownership and apparmor blocking it.