Comment 7 for bug 1756016
Revision history for this message
| james beedy (jamesbeedy) wrote Re: unexpected behavior when impi interface is on a different (but routable) network from the MAAS endpoint | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
@andreserl in one case the machine was manually added.
I am acting as a proxy for a buddy who spent the night at the data center trying to get things up and had some issues.
Possibly he didn't want to chime in here as I had directed ... just wanted to try and do it all himself.
I'll have the opportunity to get my hands on these systems more today and I'll report back with my findings.
1. Machine PXE booted using specific MAC, and it requested the config from MAAS.
True - great.
2. The machine didn't receive a config for the MAC it used to PXE boot from MAAS.
No idea, the BMC details get filled in.
3. The machine continued to request the 'default' config, which is for the enlistment environment.
True - this seems incorrect behavior, no idea why the machine was doing this.
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.
True - The user specified other mac when adding the machine manually.