Hi @ltrager, thanks for the answer but I think you misunderstood my point.
Here is my setup :
- we have a MaaS Region in a management vlan (say zone1, vlan1)
- we have a MaaS Rack in a zone with a routed vlan (say zone2, vlan2)
- in zone2, we have the untagged pxe lan which is not routed and restricted to the the MaaS Rack server and the machines in this zone (so, not accessible from zone1)
Case 1 : When we deploy a new machine without setting the network, it boots by default on the pxe lan and everything works just fine except that the machine is not accessible from anywhere else than the pxe network since it only has this one … obvious I would say.
Case 2 : Then, if we do the same but, this time, we add a vlan on top of the pxe “interface” (so, we have both pxe lan and vlan2 on the deployed machine), everything is fine but we end with both networks active on the machine.
Case 3 : Now I want to just configure the vlan2 network on the interface and exclude the pxe lan.
I do understand that it should be possible since, after pxe booting, when the machine is deployed, I understand that MaaS fallback the machine to hard drive boot and thus, the OS take over and starts its configured network which is what I want.
Problem is that in Case 3, the machine starts but it takes ages when starting the network (I suspect a timeout here) and MaaS can’t complete the deployment. Installation works well but when rebooting, the machine won’t finish the boot sequence and in MaaS, the status is stuck in “Rebooting”.
So here is my question : is this network (pxe) mandatory and why ? Or is it just a misconfiguration issue on our side ?
Any help on this would be gladly appreciated.