Comment 3 for bug 1929581

Hej,

as I needed an operational MAAS; I could not keep the broken instance, that
was not serving vlan=0. Hence,
I disabled the instance from serving those particular VLANS (10.35.0.0/24
and 10.40.0.0/24).

If the information does not give you any hints if it's a bug or just a
user error, just close it. I'll probably do a new deployment attempt in a
few weeks on different hardware. At that point, I'll check back if the
problem persists.

BR/Patrik

Den tors 27 maj 2021 kl 11:20 skrev Björn Tillenius <
<email address hidden>>:

> Which vlans/subnets are you expecting to have DHCP enabled?
>
> In the output from 'subnets read', it indicates that only "backup"
> (10.42.0/0/24) and "DBnet" (10.41.0.0/24) have DHCP enabled. Both have a
> vid > 0.
>
> ** Changed in: maas
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1929581
>
> Title:
> MAAS does not provide DHCP on default VLANs
>
> Status in MAAS:
> Incomplete
>
> Bug description:
> I’m running MAAS (snap) 3.0.0-rc1. It’s been running fine since early
> May, running as a region+rackd unit. Last week I added another rackd.
> After that, PXE booting does not work. I’ve removed the new rackd,
> hoping that it would fix it, but no change happened wrt. PXE function.
> So, I re-added it.
>
> Initially, I noticed that the /var/snap/maas/common/dhcpd.conf only
> contained the interfaces that had ‘MAAS-provided’, that were NOT
> default VLANS, i.e. only VLANS >0.
>
> Disabling, then re-enabling (a couple of times) DHCP for the default
> VLANs seems to have solved this, as now they are showing up in the
> dhcpd.conf file. I noticed no difference if it is the original
> region+rackd or the new rackd that acts as primary DHCP.
>
> This (updated dhcpd.conf) gave me some hope, but looking at the
> /var/snap/maas/common/log/dhcpd.log (or /var/snap/maas/common/maas
> /dhcpd-interfaces), it does not contain the new interfaces
> (dhcpd.conf), it only shows the old interfaces (VLAN>0). It seems that
> the log file has been updated at the same time as the dhcpd.conf was
> updated, hopefully indicating that it was restarted as the config
> changed.
>
> maas 3.0.0~rc1-10013-g.48e5645c4 14411 3.0/beta
> canonical✓ -
>
>
> Attached, you find an archive with the following files:
> dhcpd.conf
> maas.log
> rackd.log
> regiond.log (big)
> maas_rackcontrollers (output from maas $profile rackcontrollers read)
> maas_subnets (output from maas $profile subnet read)
>
> /P
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1929581/+subscriptions
>