rackd not generating a dhcpd.conf in a timely manner

[Jeff Hillman]

when restarting maas-rackd the /var/lib/maas/dhcpd.conf file is being deleted and in some instances taking more than 1 minute to be generated again.

This environment has 5 rack controllers and 2 of those rack controllers are region controllers. 5 different racks, each with their own management (PXE) network.

I have attached the sosreport from the main region controller. and also the contents of /var/log/maas (just in case sos didn't grab it)

$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-==============================-============-=================================================
ii maas 2.1.3+bzr5573-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.1.3+bzr5573-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.1.3+bzr5573-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.1.3+bzr5573-0ubuntu1~16.04.1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)

[Andres Rodriguez (andreserl)]

Hi Jeff,

I was wondering if this is still an issue?

[Jeff Hillman (jhillman)]

I do not know. I have not been in contact with that customer since.

Looping in Doug Parrish.

On Jun 27, 2017 1:02 PM, "Andres Rodriguez" <email address hidden> wrote:

> Hi Jeff,
>
> I was wondering if this is still an issue?
>
> ** Tags added: dhcp
>
> ** Changed in: maas
> Status: New => Triaged
>
> ** Changed in: maas
> Milestone: None => 2.3.0
>
> ** Changed in: maas
> Importance: Undecided => High
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1666698
>
> Title:
> rackd not generating a dhcpd.conf in a timely manner
>
> Status in MAAS:
> Triaged
>
> Bug description:
> when restarting maas-rackd the /var/lib/maas/dhcpd.conf file is being
> deleted and in some instances taking more than 1 minute to be
> generated again.
>
> This environment has 5 rack controllers and 2 of those rack
> controllers are region controllers. 5 different racks, each with
> their own management (PXE) network.
>
> I have attached the sosreport from the main region controller. and
> also the contents of /var/log/maas (just in case sos didn't grab it)
>
> $ dpkg -l '*maas*'|cat
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/
> trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version
> Architecture Description
> +++-===============================-========================
> ======-============-=================================================
> ii maas 2.1.3+bzr5573-0ubuntu1~16.04.1 all
> "Metal as a Service" is a physical cloud and IPAM
> ii maas-cli 2.1.3+bzr5573-0ubuntu1~16.04.1 all
> MAAS client and command-line interface
> un maas-cluster-controller <none>
> <none> (no description available)
> ii maas-common 2.1.3+bzr5573-0ubuntu1~16.04.1 all
> MAAS server common files
> ii maas-dhcp 2.1.3+bzr5573-0ubuntu1~16.04.1 all
> MAAS DHCP server
> ii maas-dns 2.1.3+bzr5573-0ubuntu1~16.04.1 all
> MAAS DNS server
> ii maas-proxy 2.1.3+bzr5573-0ubuntu1~16.04.1 all
> MAAS Caching Proxy
> ii maas-rack-controller 2.1.3+bzr5573-0ubuntu1~16.04.1 all
> Rack Controller for MAAS
> ii maas-region-api 2.1.3+bzr5573-0ubuntu1~16.04.1 all
> Region controller API service for MAAS
> ii maas-region-controller 2.1.3+bzr5573-0ubuntu1~16.04.1 all
> Region Controller for MAAS
> un maas-region-controller-min <none>
> <none> (no description available)
> un python-django-maas <none>
> <none> (no description available)
> un python-maas-client <none>
> <none> (no description available)
> un python-maas-provisioningserver <none>
> <none> (no description available)
> ii python3-django-maas 2.1.3+bzr5573-0ubuntu1~16.04.1 all
> MAAS server Django web framework (Python 3)...

[Blake Rouse (blake-rouse)]

This was fixed in 2.5.