Comment 0 for bug 1953049

Hi Team,
I have an issue with MaaS 2.7.3:

MaaS is not aware of all used IP addresses in a managed subnet.
    {
        "name": "internal",
        "vlan": {
            "vid": 1763,
            "mtu": 9000,
            "dhcp_on": false,
            "external_dhcp": null,
            "relay_vlan": null,
            "name": "1763",
            "fabric": "default",
            "space": "internal-space",
            "id": 5004,
            "secondary_rack": null,
            "fabric_id": 1,
            "primary_rack": null,
            "resource_uri": "/MAAS/api/2.0/vlans/5004/"
        },
        "cidr": "10.38.3.0/24",
        "rdns_mode": 2,
        "gateway_ip": null,
        "dns_servers": [],
        "allow_dns": true,
        "allow_proxy": true,
        "active_discovery": false,
        "managed": true,
        "space": "internal-space",
        "id": 3,
        "resource_uri": "/MAAS/api/2.0/subnets/3/"
    }

I checked the list of IP addresses with:

maas admin subnet ip-addresses 10.38.3.0/24 > ip_addresses.txt # (please check the attached file)
and the IP 10.38.3.78 is missing from the list even if it is used by an LXD container deployed with juju (check the juju_status.txt file)

In regiond.log I see every 5 minutes errors like this:
2021-11-23 15:40:59 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'infra-1' (4ybaww).
2021-11-23 15:40:59 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'infra-2' (sgx8m4).
2021-11-23 15:40:59 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'infra-3' (gcw8qw).
2021-11-23 15:40:59 maasserver.regiondservices.active_discovery: [info] Active network discovery: Unable to initiate network scanning on any rack controller. Verify that the rack controllers are started and have connected to the region.

Please, let me know if there is a way to fix this and update the list of used ip addresses in MaaS.
Attached is one sosreport taken from the MaaS node.

Thank you.
Regards,
Marco