DHCP issue after upgrade to MAAS 3.7

[fwendland]

I’ve recently had to update Ubuntu from 22.04 LTS to 24.04 LTS. After the update I also went ahead and updated MAAS from v3.3 to v3.7 (Debian packages). However, since then I have problems with the DHCP configuration.

So far, I’ve figured out, that /var/lib/maas/dhcpd-interfaces and the respective dhcpd_.conf are all empty. On each restart, the maas-dhcpd_.service fails, because the dhcpd_.conf files are initially missing.

On the Web UI, everything looks good. I have a fabric with VLANs and subnets defined. For some MAAS manages DHCP.

I can’t find a reason, why MAAS doesn’t pick up the DHCP configuration. Any help in troubleshooting this problem is highly appreciated.

[r00ta]

There were a bunch of DHCP-related bugs in 3.7.0 that are waiting to be released in 3.7.1 (ETA next days/early next week) 3.7.x : MAAS

I’d suggest to try 3.7/edge

[fwendland]

Thank you r00ta for the quick response. There isn’t a Debian package release for 3.7/edge, is there?

[r00ta]

maas-3.7-next : Jack-Skye Owen-Lloyd-Walters and it’s currently under certification

[osmanlicilegi]

I am not sure whether this problem has been fixed because I have some clusters affected with this bug and haven’t been fixed after upgrading to 3.7.1.

[fwendland]

@osmanlicilegi Unfortunately, I cannot provide feedback yet. I’m waiting for the next maintenance window to install the update. I’ll keep you posted.

[jim-golden]

I am having this same issue on two separate maas servers and 3.7.1 hasn’t fixed it for me. I can revert back to 3.6.2 which fixes the DHCP problem, but then I get an internal server error when trying to deploy.

Update for anyone else who may run into this after downgrading back to 3.6. The error was an issue with is_dpu being required for 3.7. I had to manually edit the database with:

“ALTER TABLE maasserver_node ALTER COLUMN is_dpu DROP NOT NULL;”

and that seems to have fixed deployments for now. I hopefully this doesn’t bite me down the road so use with caution.