I’m trying to get the simplest region+rack controller set up on 1 bare-metal Ubuntu 22.04.3 LTS machine, and have become baffled by MaaS URI/URLs and how they pertain to region/rack controllers.
I’ve installed MaaS 3.4/beta using snap, followed the instructions I found on here for creating a production postgres db (not the test one), and initialized a region+rack controller using the instructions I found here:
sudo maas init region+rack --database-uri postgres://tim:timspassword@localhost/maasdb
…but the rackd logs indicate that it cannot find the region controller:
2023-08-18 20:20:44 provisioningserver.rpc.clusterservice: [critical] Failed to contact region. (While requesting RPC info at http://<MY_MAAS_HOST>:5240/maas).
…where I answered its question about MaaS URI using the suggested one (which is the one the rackd is trying to contact in the err msg above.)
- Any ideas on what’s wrong here?
- Do I need to set MY_MAAS_HOST to localhost for the region+rack use case?
- I can successfully access via http the maas UI at http://<MY_MAAS_HOST>:5240, which redirects to http://<MY_MAAS_HOST>:5240/maas.
- I only see a single controller in the UI, a region controller (see screenshot below). When I Add rack controller, using the commands given yields a warning/error indicating that the controller has already been initialized. So, I’m convinced that the controller exists but is just not able to communicated with its regional cousin…
- I AM using an external DHCP server, and I know this isn’t supported, but this issue appears to be unrelated to that, and I have set up the DHCP server correctly to point to MaaS for TFTP. PXE clients do see the MaaS server but the tftp fails, and I assume this is because the rackd is encountering problems.
Thanks for your help.