Question about native TLS and rack controllers

Users
,
1

Hi all,

I am attempting to extend our current MAAS setup with dedicated rack controllers.
The region controller is running v3.4 with native TLS enabled on port 443 and a self signed certificate.

On the new rack controller servers I have run the following command:
sudo maas init rack --maas-url https://lab-maas01/MAAS --secret !!!

They are however unable to connect as they are unable to verify the certificate of the region controller server. Is there documentation somewhere on how to add the certificate to a rack controller running in snap?

I have imported the certificate into the machine running the rack controller and am able to login to the MAAS server api and access the API.

Thank you for any assistance you may be able to provide.

3

Some updates here:

I have verified that the snap running the rack controller can read /etc/ssl/certs/ca-certificates.crt which contains the certificate used by the region controller.
But for some reason the python program doesn’t use it with attempting to connect.

Here is also the message that is spamming the log /var/snap/maas/common/log/rackd.log

Blockquote
2024-03-14 06:48:28 provisioningserver.rpc.clusterservice: [critical] Failed to contact region. (While requesting RPC info at https://lab-maas01/MAAS).
/!-- logs truncated --!/
twisted.web._newclient.ResponseNeverReceived: [<twisted.python.failure.Failure OpenSSL.SSL.Error: [(‘STORE routines’, ‘’, ‘unregistered scheme’), (‘system library’, ‘’, ‘’), (‘STORE routines’, ‘’, ‘unregistered scheme’), (‘system library’, ‘’, ‘’), (‘SSL routines’, ‘’, ‘certificate verify failed’)]>]