maas-dhcpd not running due to missing dhcpd.conf

Bug #2015450 reported by Natalia Litvinova

This bug report will be marked for expiration in 46 days if no further activity occurs. (find out why)

10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Incomplete
Undecided
Unassigned

Bug Description

After the initial MAAS installation and some time passing dhcpd.conf dissappears:

cat /var/snap/maas/common/maas/dhcpd.conf
cat: /var/snap/maas/common/maas/dhcpd.conf: No such file or directory

As you can see in the log - the dhcp
service was running before: https://pastebin.canonical.com/p/DvpFqfjXqf/

$ sudo maas status
bind9 RUNNING pid 665699, uptime 19:09:53
dhcpd STOPPED Apr 05 02:27 PM
dhcpd6 STOPPED Not started
http RUNNING pid 623091, uptime 22:05:24
ntp RUNNING pid 622475, uptime 22:05:40
proxy RUNNING pid 631436, uptime 21:59:01
rackd RUNNING pid 621842, uptime 22:05:43
regiond RUNNING pid 621844, uptime 22:05:43
syslog RUNNING pid 622477, uptime 22:05:40

Regiond.log: https://pastebin.canonical.com/p/jT7hqztrGM/
Rackd.log: https://pastebin.canonical.com/p/XWhdRNNsZg/

I've hit this bug 2 times on different stages of the deployment.

MAAS version: 3.3.1-13169-g.94920eb1e

Currently this bug has no workaround on how to make DHCP alive again and affects the ongoing deployment

Revision history for this message
Natalia Litvinova (natalytvinova) wrote :
Revision history for this message
Natalia Litvinova (natalytvinova) wrote :
description: updated
Revision history for this message
Natalia Litvinova (natalytvinova) wrote :

subscribed ~field-critical

Revision history for this message
Igor Brovtsin (igor-brovtsin) wrote :

Requested debug logs for the issue earlier this week, marking this as incomplete for now.

Changed in maas:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
Revision history for this message
Baby Philip (babyphilip) wrote :

Issue observed in MAAS snap 3.4.1-14343-g + LXD 5.2x on a physical hardware.

Steps to reproduce:

1. Install MAAS
2. Install LXD
3. Disable dhcp and dns in lxd
4. Enable dhcp for lxd bridge in maas
5. Add LXD to MAAS
6. Deploy new VMs
7. Reboot MAAS server - dhcpd service not running and /var/snap/maas/common/maas/dhcpd.conf missing
8. Enable/Disable dhcp in MAAS Fabric UI, restores the /var/snap/maas/common/maas/dhcpd.conf and service also started

Unable to recreate this in a maas + lxd virtual environment

Baby Philip (babyphilip)
Changed in maas:
status: Expired → New
Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

@babyphilip why is this issue field-critical?

Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

Additional comment - why is LXD installed on the same host as MAAS? This is not a supported production configuration, as both LXD and MAAS will compete to manage DHCP, which requires workarounds. Moreover, deploying VMs on the same host as MAAS can exhaust machine resources and lead to outages.

Since the issue was initially reported a year ago, and it looks like the configuration is not a supported one, this issue should not be tagged as field-critical.

Since a year has passed since the original issue, there's little reason to believe that the same symptom is related to the same issue. If it continues to be a problem, please submit a new issue and include all the required logs to help us diagnose.

Changed in maas:
status: New → Incomplete
Revision history for this message
Baby Philip (babyphilip) wrote :

Thanks @jhusakowski, I believe field-critical was subscribed earlier by the original reporter. If this is not a supported production configuration, I will advise customer to segregate LXD and MAAS. I feel it would be great if this is documented as an incompatible/non-supported combination, as recently we have seen few cases with these two together.

Changed in maas:
status: Incomplete → New
status: New → Incomplete
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.