Doing a fresh install using AWS EC2 t2.xlarge with RHEL-9.3.0. After spinning up the VM, I registered the instance with subscription-manager and went to management.umh.app/instance/add to create an UMH Only instance. Copy and pasted the command and k3s.service failed to start. Did a

systemctl status k3s.service

Turns out that

!

inverts the status whatever you just executed. Pretty much k3s.service does NOT want nm-cloud-setup.service to be enabled. So I ran

sudo systemctl disable nm-cloud-setup.service

and ran the UMH command again.. VOILA she works!

That is interesting! I know we are doing automated end to end tests with every (!) single release of the UMH with RHEL. But maybe not with version 9, but an older version. @Ferdinand can you check? Maybe for a newer RHEL version we need to adjust the commands a little bjt

We currently run:

bash
# Disable nm-cloud-setup.service
handleCheck "Checking if nm-cloud-setup.service is enabled..."
if systemctl list-units --full --all | grep -Fq 'nm-cloud-setup.service'; then
    handleStep "nm-cloud-setup.service is enabled. Disabling nm-cloud-setup.service..."
    if ! systemctl disable --now nm-cloud-setup.service >> /tmp/mgmt_install.log 2>&1; then
        handleError "Failed to disable nm-cloud-setup.service." "Manually disable nm-cloud-setup.service using 'sudo systemctl disable --now nm-cloud-setup.service' and run the script again."

    fi
    handleSuccess "nm-cloud-setup.service is disabled successfully."
else
    handleSuccess "nm-cloud-setup.service is already disabled."
fi

in our automatic installer. It's checked against 9.2.X

[root@aether ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 9.2 (Plow)

Ill now setup a new 9.3 VM and check against it

oh interesting, thank you!