[2.2b3] MAAS reports DHCP is running but it is not

Bug #1673433 reported by Andres Rodriguez
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Expired
High
Unassigned

Bug Description

MAAS reports that DHCP is successfully running (under the controllers page), but it is not. This is what I see in syslog:

Mar 16 11:32:45 maas22 dhcpd[2077]: Can't open /var/lib/maas/dhcpd.conf: Permission denied
Mar 16 11:32:45 maas22 dhcpd[2077]:
Mar 16 11:32:45 maas22 dhcpd[2077]: If you think you have received this message due to a bug rather
Mar 16 11:32:45 maas22 dhcpd[2077]: than a configuration issue please read the section on submitting
Mar 16 11:32:45 maas22 dhcpd[2077]: bugs on either our web page at www.isc.org or in the README file
Mar 16 11:32:45 maas22 dhcpd[2077]: before submitting a bug. These pages explain the proper
Mar 16 11:32:45 maas22 systemd[1]: maas-dhcpd.service: Main process exited, code=exited, status=1/FAILURE
Mar 16 11:32:45 maas22 dhcpd[2077]: process and the information we find helpful for debugging..
Mar 16 11:32:45 maas22 dhcpd[2077]:
Mar 16 11:32:45 maas22 dhcpd[2077]: exiting.
Mar 16 11:32:45 maas22 systemd[1]: maas-dhcpd.service: Unit entered failed state.
Mar 16 11:32:45 maas22 systemd[1]: maas-dhcpd.service: Failed with result 'exit-code'.

Changed in maas:
importance: Undecided → Critical
milestone: none → 2.2.0
status: New → Triaged
rahmadani (rahmadani)
Changed in maas:
assignee: nobody → rahmadani (rahmadani)
Revision history for this message
Michael Iatrou (michael.iatrou) wrote :

Same issue is observed with maas 2.2.0~beta4+bzr5856-0ubuntu1~16.04.1

Jeremy Bícha (jbicha)
Changed in maas:
assignee: rahmadani (rahmadani) → nobody
Changed in maas:
milestone: 2.2.0 → 2.2.x
Changed in maas:
milestone: 2.2.x → 2.3.x
Changed in maas:
milestone: 2.3.x → 2.4.0beta1
Changed in maas:
milestone: 2.4.0beta1 → 2.4.0beta2
Changed in maas:
importance: Critical → High
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.