Comment 1 for bug 1798671

The attached screen shot shows the MAAS UI reporting three completely different IP addresses that don't work, while the MAAS log instead shows two OTHER IP Addresses that DO work. Basically, the IP addresses below in the maas.log snippet are the IP addresses MAAS assigned when I set those two interfaces to "Auto Assign". When I entered Rescue Mode, MAAS UI tells me completely differetn IP addresses that do not work, while the 2.99 address DOES work.

2018-10-18T15:49:58.420531-04:00 critical-maas maas.node: [info] shilin: Status transition from READY to ALLOCATED
2018-10-18T15:49:58.435239-04:00 critical-maas maas.node: [info] shilin: allocated to user bladernr
2018-10-18T15:49:58.891890-04:00 critical-maas maas.interface: [info] Allocated automatic IP address 10.0.2.99 for enp2s0 (physical) on shilin.
2018-10-18T15:49:59.020529-04:00 critical-maas maas.interface: [info] Allocated automatic IP address 10.0.2.100 for enp3s0 (physical) on shilin.
2018-10-18T15:49:59.052759-04:00 critical-maas maas.node: [info] shilin: Status transition from ALLOCATED to DEPLOYING
2018-10-18T15:49:59.138464-04:00 critical-maas maas.power: [info] Changing power state (on) of node: shilin (aday6p)
2018-10-18T15:50:19.250680-04:00 critical-maas maas.power: [info] Changed power state (on) of node: shilin (aday6p)
2018-10-18T16:02:52.834245-04:00 critical-maas maas.node: [info] shilin: Releasing node
2018-10-18T16:02:52.837102-04:00 critical-maas maas.node: [info] shilin: Status transition from DEPLOYING to RELEASING
2018-10-18T16:02:52.865662-04:00 critical-maas maas.node: [info] shilin: Status transition from RELEASING to BROKEN
2018-10-18T16:02:52.971381-04:00 critical-maas maas.power: [info] Changing power state (off) of node: shilin (aday6p)
2018-10-18T16:03:01.703957-04:00 critical-maas maas.power: [info] Changed power state (off) of node: shilin (aday6p)
2018-10-18T16:03:06.517515-04:00 critical-maas maas.node: [info] shilin: Status transition from BROKEN to ENTERING_RESCUE_MODE
2018-10-18T16:03:06.593978-04:00 critical-maas maas.power: [info] Changing power state (cycle) of node: shilin (aday6p)
2018-10-18T16:03:06.595416-04:00 critical-maas maas.node: [info] shilin: Rescue mode starting
2018-10-18T16:03:27.178453-04:00 critical-maas maas.power: [info] Changed power state (on) of node: shilin (aday6p)
2018-10-18T16:04:48.985965-04:00 critical-maas maas.node: [info] shilin: Status transition from ENTERING_RESCUE_MODE to RESCUE_MODE

bladernr@critical-maas:~$ for x in 10.0.1.0 10.0.1.1 10.0.1.2 10.0.2.99 10.0.2.100; do
> ping -c 1 $x
> done
PING 10.0.1.0 (10.0.1.0) 56(84) bytes of data.
From 10.0.0.1 icmp_seq=1 Destination Host Unreachable

--- 10.0.1.0 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

PING 10.0.1.1 (10.0.1.1) 56(84) bytes of data.
From 10.0.0.1 icmp_seq=1 Destination Host Unreachable

--- 10.0.1.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

PING 10.0.1.2 (10.0.1.2) 56(84) bytes of data.
From 10.0.0.1 icmp_seq=1 Destination Host Unreachable

--- 10.0.1.2 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

PING 10.0.2.99 (10.0.2.99) 56(84) bytes of data.
64 bytes from 10.0.2.99: icmp_seq=1 ttl=64 time=0.317 ms

--- 10.0.2.99 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.317/0.317/0.317/0.000 ms
PING 10.0.2.100 (10.0.2.100) 56(84) bytes of data.
From 10.0.0.1 icmp_seq=1 Destination Host Unreachable

--- 10.0.2.100 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms