Installing MAAS 3.5 on non-ubuntu hosts

installed maas 3.5.2-16329-g.a0861379f ( snap) on rhel 8.9

maas status
Service Startup Current Since
agent disabled inactive -
apiserver enabled active today at 15:28 UTC
bind9 disabled active today at 15:28 UTC
dhcpd disabled inactive -
dhcpd6 disabled inactive -
http disabled inactive -
ntp disabled active today at 15:28 UTC
proxy disabled active today at 15:28 UTC
rackd enabled backoff today at 15:31 UTC
regiond enabled active today at 15:28 UTC
syslog disabled active today at 15:28 UTC
temporal disabled active today at 15:28 UTC
temporal-worker disabled active today at 15:28 UTC

logs showing a host of issues. Am I missing something obvious from the pre requisites?
the maas init command runs without issue.

eg temporalio.exceptions.ApplicationError: Could not retrieve the IP addresses of the region controller ‘ktrdqq’ from the API. This activity will be retried until we have the IP for all the region controllers.

[4429]: 2025-01-09T15:28:55.360Z [pebble] POST /v1/services 65.680014ms 202
[4429]: 2025-01-09T15:28:55.362Z [pebble] GET /v1/services?names=proxy 65.231345ms 200
[4429]: 2025-01-09T15:28:55.363Z [pebble] Service “http” starting: sh -c “exec systemd-cat -t maas-http $SNAP/bin/run-nginx”
[4937]: 2025/01/09 15:28:55 [emerg] 4937#4937: socket() [::]:5240 failed (97: Unknown error)

maas-regiond[4462]: provisioningserver.utils.services: [critical] Failed to update and/or record network interface configuration: Couldn’t listen on :::5240: [Errno 97] Address family not supported by protocol.; interf aces: {‘ens192’: {‘type’: ‘physical’, ‘mac_address’: ‘xx:xx:xx:xx:xx:xx’, ‘links’: [{‘mode’: ‘static’, ‘address’: ‘#.#.#.#/24’, ‘gateway’: ‘#.#.#.#’}], ‘enabled’: True, ‘parents’: , ‘source’: ‘machine-resources’, ‘monitored’: True}}

Hey

RHEL is not supported as host for MAAS. See Bug #2083710 “Temporal Fails to Start on MAAS 3.5 (Fresh Install...” : Bugs : MAAS . Please use Ubuntu

is this just a 3.5 issue that will be fixed at one point?

https://snapcraft.io/install/maas/rhel

I’m confused on the stance of whether it is supported or not on rhel.

It’s not on the top of the priority list. If community can help to fix it I’m happy to review the patch!

I have a clean and efficient solution for this, which I’ll share soon!

We’re successfully running MAAS 3.5.2 on Oracle 9 hosts, including both Region and Rack controllers. The setup uses MAAS Debian packages, which I believe remain the best option, running on Ubuntu containers with systemd. No SNAPs are involved.

Cheers!