Comment 6 for bug 1756016
Revision history for this message
| Andres Rodriguez (andreserl) wrote Re: enlisting and commissioning breaks when a node impi interface is on a different (but routable) network from the MAAS endpoint | #6 |
James,
Your bug title and description do not match. There's no relationship between the BMC and a machine when the machine requests the PXE process, so it doesn't really matter in what network the BMC is connected, as the BMC doesn't do the PXE process.
From the information you have provided, it is completely clear that:
1. Machine PXE booted using specific MAC, and it requested the config from MAAS.
2. The machine didn't receive a config for the MAC it used to PXE boot from MAAS.
3. The machine continued to request the 'default' config, which is for the enlistment environment.
4. The machine booted into enlistment environment, tried to register itself, but failed because one or more MAC addresses (other than the one used for PXE) are already known to MAAS.
So to me, what it looks like is that a machine is already registered in MAAS with some of the MAC addresses that belong to the machine, but not with the MAC address the machine is using to PXE boot. Since MAAS doesn't know such MAC address, then it doesn't know it needs to PXE the machine for commissioning.
MAAS requires that *at least* the PXE mac address/interface is provided when manually adding a node.
Can you confirm how was this machine you are attempting to commission added to MAAS?