Host deploys with the wrong VLAN

[William Edwards]

Hello,

I have been experiencing problems where, upon deploying an Ubuntu node, the
network configuration of the node changes after the install, and becomes
inaccessible. Adding and commissioning the node in MaaS works perfectly
fine, and even the install log is reported back to the MaaSserver. Before
deploying the node, I selected one of our VLANs (VLAN 11) and set it to use
DHCP, but after the install, the network configuration reflected in the web
UI changes to VLAN 10 after the installation completes.

I currently have a rack controller on VLAN 10, with DHCP & DNS disabled, so
it can be handled by an external service, and our our DHCP service is
configured to allow machines to PXE boot off of the rack controller in VLAN
10. The PXE booting across VLANs itself works perfectly fine.

If I deploy a node on the same VLAN that the rack controller is on,
everything works as expected.

Is this a bug? Shouldn't it be possible to deploy a node from rack
controllers in different VLANs?

Regards,
William
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20180208/2d7e6dfd/attachment.html>