MAAS 3.7 wrong next-server IP in dhcpd config on rack controller

Users
1

We have the following setup (with anonymized IPs)

Region Controller:

  • eth0 on MAAS VLAN, managed by this controller; IP 10.0.0.1
  • eth1 on management VLAN, unmanaged by MAAS; IP 192.168.0.1

Rack Controller:

  • eth0 on MAAS VLAN; IP 10.0.0.2

We recently upgraded from 3.6.2 to 3.7.0 and observed that the dhcpd.conf on the rack controller went from containing

shared-network vlan-1 {
    subnet 10.0.0.0 netmask 255.255.255.0 {
        next-server 10.0.0.2

to

shared-network vlan-1 {
    subnet 10.0.0.0 netmask 255.255.255.0 {
        next-server 192.168.0.1

All instances of the original IP in the dhcpd.conf file were replaced by the unmanaged IP of the region controller. MAAS manages DNS in this environment and there is no conflict between hostnames or DNS entries of the rack or region controllers.

This appeared in MAAS 3.7.0 and disappeared when reverting to MAAS 3.6.2, returning to the original behavior.

2

Fixed in Bug #2134485 “MAAS 3.7.0: DHCP Fails on Split Region/Rack with V...” : Series 3.7 : Bugs : MAAS

1 Like