incorrect interface data reported in juju status

[Rodrigo Barbieri]

juju version: 2.9.27

on a maas-provided openstack deployment the following is reported in juju status:

"machines": {
    "0": {
...
        "br-ens3": {
          "ip-addresses": [
            "10.10.10.101"
          ],
          "mac-address": "46:6a:06:2a:f1:36",
          "gateway": "10.10.10.1",
          "space": "oam",
          "is-up": true
        },
        "ens3": {
          "ip-addresses": [
            "10.10.10.101"
          ],
          "mac-address": "52:54:00:2b:5e:10",
          "gateway": "10.10.10.1",
          "space": "oam",
          "is-up": true
        },

where it shows ens3 as being a valid interface with IP address. SSH'ing into the machine however, we can see:

2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-ens3 state UP group default qlen 1000
    link/ether 52:54:00:2b:5e:10 brd ff:ff:ff:ff:ff:ff
9: br-ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 46:6a:06:2a:f1:36 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.101/24 brd 10.10.10.255 scope global br-ens3
       valid_lft forever preferred_lft forever
    inet6 fe80::446a:6ff:fe2a:f136/64 scope link
       valid_lft forever preferred_lft forever

[John A Meinel (jameinel)]

At one point we had an issue where once we saw an IP address on a machine (on a particular interface) we would start tracking it, but we wouldn't clean up if that ever went away. However, I thought we had fixed that particular one, though the interface itself hasn't gone away, so I'm wondering if we successfully notice if the IP or Interface is gone entirely, but in this case the IP is still present, and the Interface is still present, it is just no longer associated with that interface.

[Canonical Juju QA Bot (juju-qa-bot)]

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.