Rogue DHCP server not detected; enlist fails

[Julian Edwards]

I see this error:

cmd #0025: {{{ssh -i /home/ubuntu/.config/maas-test/vm_ssh_id_rsa -o
LogLevel=quiet -o UserKnownHostsFile=/dev/null -o
StrictHostKeyChecking=no ubuntu@192.168.122.226 LC_ALL=en_US.UTF-8
ipmipower -h 10.0.0.101 -u maas -p 6rFuvt3r --on}}}
cmd #0025 retcode: {{{0}}}
cmd #0025 stdout: {{{10.0.0.101: ok}}}

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/maastest/cases.py", line 227,
in test_enlist_node
    self.fail("Failed to enlist node.")
  File "/usr/lib/python2.7/unittest/case.py", line 412, in fail
    raise self.failureException(msg)
AssertionError: Failed to enlist node.

Which means the IPMI command worked and then there is no further feedback at all other than the ugly traceback.

The node was indeed powered on but I've no idea why it didn't go further.

[Julian Edwards (julian-edwards)]

Ok I see why now - there is a rogue DHCP server that the initial checks have not picked up.

[Jeroen T. Vermeulen (jtv)]

A bit more detail about the setup that triggered this: MAAS was installed on the host, and had its DHCP server running on the same network interface that maas-test was told to use. The DHCP check in maas-test failed to detect it.

Our working hypothesis is that this is because having the DHCP server and client on the same network interface is a special case (e.g. because the server ignores a discovery request coming from its own interface).