Error while calling ScanNetworks: Unable to get RPC connection for rack controller

MAAS core team cannot access the support portal to view your sosreports. please attach them directory to this bug, without the link.

Hi Bill,
unfortunately, I cannot upload it. I think the issue is related to the size of the file (around 400MB) and launchpad drops the connections after a while when I start the upload.
Please let me know if there is another way.

Thank you.
Regards,
Marco

Could you please attach just regiond.log and rackd.log?

We can start from there and ask for more logs if needed.

Also, you mentioned the 10.38.3.78 IP from juju status, but the IP in the output is actually 10.38.0.70, so you'll have to check in the IPs for the 10.38.0.0/24 subnet.

Hi Alberto,
the output of "juju status" only shows a single ip, but the container has multiple IPs.

Here is the output of "ip addr"

27: eth0 inet 10.38.2.74/24 brd 10.38.2.255 scope global eth0\ valid_lft forever preferred_lft forever
27: eth0 inet6 fe80::216:3eff:fe84:2037/64 scope link \ valid_lft forever preferred_lft forever
29: eth1 inet 10.38.3.78/24 brd 10.38.3.255 scope global eth1\ valid_lft forever preferred_lft forever
29: eth1 inet6 fe80::216:3eff:fef8:b030/64 scope link \ valid_lft forever preferred_lft forever
31: eth2 inet 10.38.0.57/24 brd 10.38.0.255 scope global eth2\ valid_lft forever preferred_lft forever
31: eth2 inet6 fe80::216:3eff:fec9:306b/64 scope link \ valid_lft forever preferred_lft forever

Regards,
Marco

Hi Marco, would it be possible to upgrade MAAS to a more recent version, and check if the error still occurs?

Hi Alberto,
probably yes. I'll update the bug as soon as possible.

Thank you.
Regards,
Marco

[Expired for MAAS because there has been no activity for 60 days.]

I am seeing this behaviour as well.

However, I only have one network interface, only one ip address, and only one region+rack controller; so it has no other controllers to talk to.

Server information attached.

$ ip addr
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: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:92:04:e7:c5:e9 brd ff:ff:ff:ff:ff:ff
    inet 10.100.127.223/21 brd 10.100.127.255 scope global enp0s31f6
       valid_lft forever preferred_lft forever
    inet6 fe80::a92:4ff:fee7:c5e9/64 scope link
       valid_lft forever preferred_lft forever
it@maas-temp:/var/snap/maas/current$ snap list maas
Name Version Rev Tracking Publisher Notes
maas 3.2.6-12016-g.19812b4da 23947 3.2/stable canonical✓ -

Still need the logs to be able to start debugging this issue.

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.

Hi mitzone,

Can you please check that your database is healthy and all tables are in place?

1. Is it a fresh MAAS install?
2. When you did `maas init` were there any errors during DB migration?

2023-03-10 22:40:37 maasserver.start_up: [error] Database error during start-up
Traceback (most recent call last):
  File "/snap/maas/26274/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.UndefinedTable: relation "maasserver_config" does not exist
LINE 1: ..._config"."name", "maasserver_config"."value" FROM "maasserve...
                                                             ^

Hello,
I have this behaviour on a fresh install of 3.3.x latest and 3.2.7 for both DEB and SNAP installs.
I'm not running any HA setup anymore.
Region and rack on same box. ScanNetworks not working.
Thank you.

1. When you did `maas init region+rack` were there any errors during DB migration step?
2. Are you using standalone PostgreSQL?
3. Were there any errors in PostgreSQL logs during the initial MAAS setup?

I just did a fresh installation of MAAS and `maas init` completed without any errors.
Could it be something with your database?

So after a fresh (no DB migration, no nothing) install of MAAS 3.2.7 from SNAP (same issue for DEB) for ex.
Everything seems to work correctly, I can enroll/commission/deploy, but I see this error every 5 minutes or so in my logs :

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.regiondservices.active_discovery: [info] Active network discovery: Unable to initiate network scanning on any rack controller.

I thought this might be only cosmetic, so I booted up 2 machines not managed by MAAS in the same subnet, and their IPs were not populated in MAAS as being used, so definetly Active network discovery is not working.

Thanks.

I just did a clean install and I don't see any errors that you do have in your log. It might be something with your installation.

What OS and version are you using? Are there any CIS hardened configs?

The error I've pointed to in https://bugs.launchpad.net/maas/+bug/1953049/comments/22
Says that `maas init` (installation) was not completed successfully and you are missing some tables.

There are also several FileNotFoundError in you rack logs.
E.g.
builtins.FileNotFoundError: [Errno 2] No such file or directory: '/var/snap/maas/26274/proxy/.maas-proxy.conf.l7aj2oa9.tmp'

That file is also normally being created.

So far I am not able to reproduce it with 3.2.7 snap and focal

Ok, I'll reinstall.
The logs I posted here are from a DEB deployment with HA (2 region controllers and 2 rack controllers). In otrder to bring up the second region controller, it's normal I think to have those errors until you point it to the correct DB server and etc.

Will do a fresh 3.2.7 SNAP install again and will come back.

Same issue

Test box:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS"
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"

kernel 5.4.0-88-generic

Installed MAAS from snap like this :

1. snap install --channel=3.2 maas
2. snap install maas-test-db
3. maas init region+rack --database-uri maas-test-db:///
4. maas createadmin

Then from GUI I went to Subnets, selected my subnet, clicked edit and checked Active discovery box (default is off)

Waited some time, same error entries in regiond started to pop up every 5 minutes.
Attached logs.
Thank you.

mitzone, sorry I somehow missed that `Active discovery` on a Subnet should be enabled.

I am able to reproduce this as well.

Moved `bug-council` tag from #1769471