Comment 21 for bug 1953049

I am too seeing errors about not being able to initialize ScanNetwork

2023-03-11 01:36:40 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'maas-test-rack1' (6h7sx7).
2023-03-11 01:36:40 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'maas-test-rack2' (4sq738).
2023-03-11 01:36:40 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.
2023-03-11 01:37:49 regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2023-03-11 01:39:19 regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2023-03-11 01:41:40 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'maas-test-rack1' (6h7sx7).
2023-03-11 01:41:40 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'maas-test-rack2' (4sq738).
2023-03-11 01:41:40 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.

running snap 3.2.7 on Ubuntu 20
Setup is 2 x region controllers and 2 x rack controllers.

I attached the regiond and rackd logs for all.
Thanks.