MAAS erroneously assumes that it must have a unique interface for an unmanaged network

[Mike Pontillo]

I'm using DD-WRT with the following DNSMasq options set:

dhcp-boot=pxelinux.0,,172.16.100.10

172.16.100.10 is the address of an off-link MAAS server.

When I try to add a second cluster interface, I'm not really sure what interface or IP address to specify, so I type "eth0" (which conflicts with an on-link interface) and get an internal server error. The stack trace in the log[1] shows that 'Another cluster interface already connects network interface eth0 to an IPv4 network'.

I should be able to add unmanaged cluster "interfaces" without specifying an interface name.

(also, I assume that the "IP address", in this case, must be an IP address on the cluster reachable by the deployed node.)

I tested this under MAAS 1.8; everything works up to the point of deployment, except that upon deployment, the node contacts the DHCP server's IP address to try to report back to MAAS, and never completes successfully.

In 1.9 this should work properly.

[1]:
http://paste.ubuntu.com/13485939/

[Mike Pontillo (mpontillo)]

Workaround: specify any interface name, such as "bogus0".

[Andres Rodriguez (andreserl)]

Hi!

We believe this is no longer an issue in the latest MAAS releases. As such, we are marking this bug report as invalid. If you believe this is still an issue, please re-open this bug report.

Thanks

[Mike Pontillo (mpontillo)]

This became invalid in MAAS 2.x, but is a Won't Fix for MAAS 1.x.