Comment 5 for bug 1792965

Just for the record this is not a 2.3.5 bug, but instead is occurring on
2.4.2.

On Wed, Nov 21, 2018 at 9:30 AM Andres Rodriguez <email address hidden>
wrote:

> As per discussion on the call:
>
> 1. This issue has been seen multiple times most recently.
> 2. Solutions QA has changed the way how they install and configure MAAS,
> by re-using a previously used hardware.
> 3. MAAS 2.3.5 has not changed in quite a while.
> 4. Since there's been environmental changes, this could be related and the
> reason why this issue surfaces.
>
> AS such, given that the error message clearly shows that there's another
> DHCP server running when MAAS' DHCP is being brought up, could you
> please provide the following information:
>
> 1. The steps you take you install MAAS on your re-usable environment and
> any logs of the installation process (e.g. /var/log/apt/{history,term}.log
> of the installation)
> 2. The steps you take to clean-up your environment
> 3. After cleaning up your environment, is isc-dhcp installed? is isc-dhcp
> left running? (ps faux | grep dhcpd && dpkg -l | grep isc-dhcp)
>
>
> ** Changed in: maas
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1792965
>
> Title:
> MAAS-dhcpd fails to start, commissioning fails
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1792965/+subscriptions
>

--

Chris Gregan
Engineering Manager
Solutions QA/Techops
<email address hidden>