[2.1.3] When commissioning a 'NEW' machine from the Machine details page, it incorrectly shows 'MAAS is not providing DHCP.' message

[Larry Michel]

I had recently enabled DHCP for the vlan and as I am getting ready to commission, MAAS is showing message that it's not providing DHCP which I know to be false since machine had just enlisted. I tried new sessions and reloading, but the warning does not go away.

ubuntu@maas2-production-new:~$ 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)]

@Larry,

This could be that the rack controller had disconnected, and as such, the dhcp service was down or was being restarted at the time.

Also, can you confirm this is 2.1.3 and not 2.2 ?

[Brendan Donegan (brendan-donegan)]

I have seen this - I have a particular set of tests which seem to enlist the nodes but those nodes interfaces are not connected to a subnet. Can you check after enlisting what the Interface info looks like for the nodes?

[Brendan Donegan (brendan-donegan)]

Actually, after double checking, the interface info bit doesn't seem to be relevant.

[Larry Michel (lmic)]

@Andres, this is for 2.1.3. I don't recall seeing it when we tested with 2.2. The rack controller is connected and I am seeing it consistently, even today.

[Fabian Schroedter (fabiansc)]

FYI: I am also experiencing this behaviour.

1. DHCP is configured
2. IP of the MAAS range is assigned to new node
3. Nmap displays the IP of the new node (nmap is executed on the maas server)
4. New node is beeing shut down by MAAS and enlisted within "NODES" as Status "NEW"
5. When commissioning a warning message is displayed "MAAS is not providing DHCP."
   Commissioning fails due to missing IP configuration for the new node.
   Nmap also shows that the new node does not receive any new IP. Minimal network traffic (e.g. DHCP request) on the new node.

That's a blocker for me.

[Fabian Schroedter (fabiansc)]

In case of reproduction steps:
I documented my complete setup (starting from scratch / blank Hardware) in my blog: https://cloud.fas-consulting.de/drupal/page/cloud-computing/metal-service-maas

I am currently running on MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1) with the issue.

[Fabian Schroedter (fabiansc)]

Hi again,

I just created another VM on my server to provide the MAAS log file. The node gets the IP 192.168.200.106 and is identified within MAAS.

Mar 31 23:15:58 Nexus maas.interface: [info] enxb827ebf3bacf (physical) on Nexus: New MAC, IP binding observed: 00:00:00:00:00:01, 192.168.200.106
Mar 31 23:17:15 Nexus maas.import-images: [info] Started importing boot images.
Mar 31 23:17:15 Nexus maas.import-images: [info] Downloading image descriptions from http://192.168.200.1:5240/MAAS/images-stream/streams/v1/index.json
Mar 31 23:17:17 Nexus maas.import-images: [info] Updating boot image iSCSI targets.
Mar 31 23:17:19 Nexus maas.import-images: [info] Downloading image descriptions from http://images.maas.io/ephemeral-v3/daily/
Mar 31 23:17:21 Nexus maas.import-images: [info] Finished importing boot images, the region does not have any new images.
Mar 31 23:17:31 Nexus maas.bootsources: [info] Updated boot sources cache.
Mar 31 23:17:32 Nexus maas.bootresources: [info] Started importing of boot images from 1 source(s).
Mar 31 23:17:32 Nexus maas.import-images: [info] Downloading image descriptions from http://images.maas.io/ephemeral-v3/daily/
Mar 31 23:17:35 Nexus maas.bootresources: [info] Importing images from source: http://images.maas.io/ephemeral-v3/daily/
Mar 31 23:19:30 Nexus maas.api: [info] mint-owl: Enlisted new machine

Afterwards the VM has been shut down by MAAS:

ubuntu@Noctua:~$ virsh list --all
 Id Name State
----------------------------------------------------
 - foo shut off

[Fabian Schroedter (fabiansc)]

Hi,

I upgraded to MAAS Version 2.1.5+bzr5596-0ubuntu1 (16.04.1). Please find an update below:

Client-Host:
ubuntu@Noctua:~$ virt-install --connect qemu:///system -n bar -r 2048 --vcpus=2 -f /home/ubuntu/kvm/vhd/boo.img -s 20 --noautoconsole --os-type linux --accelerate --network=bridge:br0 -m 00:00:00:00:00:02 -k de --pxe

Starting install...

Allocating 'bar.img' | 20 GB 00:00:00
Creating domain... | 0 B 00:00:01
Domain installation still in progress. You can reconnect to
the console to complete the installation process.
ubuntu@Noctua:~$
ubuntu@Noctua:~$ virsh list --all
 Id Name State
----------------------------------------------------
 2 bar running
 - foo shut off

MAAS Server:
Apr 20 14:48:43 Nexus maas.interface: [info] enxb827ebf3bacf (physical) on Nexus: New MAC, IP binding observed: 00:00:00:00:00:02, 192.168.200.107
Apr 20 14:57:28 Nexus maas.import-images: [info] Started importing boot images.
Apr 20 14:57:32 Nexus maas.import-images: [info] Downloading image descriptions from http://192.168.200.1:5240/MAAS/images-stream/streams/v1/index.json
Apr 20 14:57:34 Nexus maas.import-images: [info] Downloading boot resources from http://192.168.200.1:5240/MAAS/images-stream/streams/v1/index.json
Apr 20 14:57:59 Nexus maas.bootresources: [info] Finished importing of boot images from 1 source(s).
Apr 20 14:58:08 Nexus maas.api: [info] rich-piglet: Enlisted new machine

Still error: MAAS is not providing DHCP.

[Felipe Reyes (freyes)]

Running 2.1.5 , I was seeing this problem, upgrading to 2.2-rc2 made it go away.

[Andres Rodriguez (andreserl)]

It seems that the problem went away in MAAS 2.2. As such, I'm marking this as invalid. If you believe the bug still exists, please re-open the bug report.