Comment 0 for bug 1803188

I commissioning a machine (which happened to be a VM inside a MAAS deployed Pod), and the interface obtained two different IP addresses during commissioning.

The network commissioning script captured this and created a new interface in the machine with Ready state. The commissioning output for interfaces show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:0f:2d:94 brd ff:ff:ff:ff:ff:ff
    inet 10.90.90.225/24 brd 10.90.90.255 scope global ens4
       valid_lft forever preferred_lft forever
    inet 10.90.90.198/24 brd 10.90.90.255 scope global secondary ens4
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fe0f:2d94/64 scope link
       valid_lft forever preferred_lft forever

The resulting machine, please see attached screenshot.

That said, this doesn't seem like an issue isolated to machines inside a pod.