On a physical host that is running as a region+rack controller (3.5 stable), with multiple VLAN tagged interfaces to a single bonded interface, the active discovery process does not yield any results. I see log messages indicating the discovery process is running, however, nothing appears in the UI. If I run a manual nmap scan on the same host, it is able to detect hosts as expected.
Is this an issue with using bonded interfaces or multiple VLAN-tagged interfaces?
There is minimal documentation that exists, so looking for any advice or nuance to getting this feature functional.
Hi, I just tried to get the same installation as you, and ended up with the same result:
MAAS 3.5.4 using snap installation on a Ubuntu 24.04.2 LTS host, all in one OR splitted apart nodes, network discovery doesn’t work at all on mixed untagged/tagged vlan nodes as maas constantly try to use the untagged nic to discover networks instead of using the vnic.
Also, I’ve tried the same setup on an isolated untagged native vlan environment, the discovery does works as it find out correctly the nodes isolated on this specific vlan BUT the WebUI doesn’t work and is utterly broken as it can’t list the discovered nodes.
I’ve validated that using tcpdump on nodes to validate that our rackd controller does indeed correctly and actively ARP scan the network using nmpa AND that our nodes on that network does answer correctly. It just work, the discovery is correctly performed and stored within the regiond controller database BUT the WebUI page can’t get it displayed correctly.
From my own investigation, it comes from the page not being able to properly display the API payload as it’s the only endpoint that doesn’t work correctly, I successfully get the node list using API/CLI and looking at the DB.
I don’t know if it can help you as your post is quite old now, but I hope it will help other on the internet ^^
