The only section where I see this would affect would be ipmi autodetection. Do the nodes in Ready state have CPU/Memory values?
Now, MAAS requires Internet access (or archive access in such case) in order to be able to obtain packages and be able to install the packages it needs. I'm assuming that this is the same case for the Debian Installer. Unfortunately, this is not really a bug in MAAS itself. During the commissioning process, it is cloud-init the one in charge of configuring network interfaces. Cloud-init only waits (and configures) DHCP on BOOTIF (being this the network interface where it is PXE booting from), and does not configure any other network interface. This means that if your MAAS network does not have external network access, then the commissioning environment wont be able to install packages because the network it PXE Booted from will be the only configured network interface. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1185261 Title: MaaS nodes being enlisted with multiple network cards fail to commission To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1185261/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
