MAAS

  1. Bug #1575815
  2. Comment #12

Comment 12 for bug 1575815

Revision history for this message
Larry Michel (lmic) wrote : Re: NIC previously discovered through commissioning no longer connected to Maas network

Hi Andres,
It's just normal operation, no upgrade, no commissioning. It happened on a Saturday and no one would have been accessing the maas server at that time AFAICT.

I don't know any sequence to recreate since this happened during automated deployments, but I narrowed this issue possibly surfacing for krastin server during the time window from that section of the maas log: https://pastebin.canonical.com/156722/

The warning message that's rather strange is this one:
May 14 12:08:42 maas-integration-september maas.interface: [WARNING] Auto IP address (10.244.192.169) on krastin.oilstaging was deleted because it was handed out by the MAAS DHCP server from the dynamic range.

The problem is that 10.244.192.169 is from the static range.

DHCP dynamic IP range low value

10.244.224.0
Lowest IP number of the range for dynamic IPs, used for enlistment, commissioning and unknown devices.

DHCP dynamic IP range high value

10.244.240.255
Highest IP number of the range for dynamic IPs, used for enlistment, commissioning and unknown devices.

Static IP range low value

10.244.192.152
Lowest IP number of the range for IPs given to allocated nodes, must be in same network as dynamic range.

Static IP range high value

10.244.196.255
Highest IP number of the range for IPs given to allocated nodes, must be in same network as dynamic range.