Using the tarball installation method on Centos8 causes "Unable to watch for tunnel endpoints..." error about rke2-ansible HOT 3 CLOSED

Per #41, there seems to be a typo in either the tarball_install README.md or the playbook. I tried downloading rke2-images.linux-amd64.tar.gz and leaving the playbook unmodified, which produced the same error described above. I tried changing references to rke2-images.linux-amd64.tar.gz in the playbook to rke2-images.linux-amd64.tar.zst, which produced the same error described above.

from rke2-ansible.

I don't think that the issue is related with the tarball or image deployment. Got the same when deploying with selinux: true and cis-profile 1.6 on rhel8.4 (which is currently not supported).

After turning selinux off and restarting the services, it worked like charm

Check https://docs.rke2.io/install/requirements.html for CentOs

from rke2-ansible.

Ah, thanks for pointing out my silly mistake. I should've noticed that RKE2 only supports Centos 8.2. After rolling my Target VM back to CentOS 8.2 and disabling SELinux, everything runs as expected. I am testing now to see if installing the rke2-selinux RPM will result in the rke2 server running as expected, with SELinux enabled on the Target VM, per the instructions here: https://github.com/rancherfederal/rke2-ansible/blob/main/tarball_install/README.md

For anyone else's reference, in case they run into this issue when switching to running the air-gapped method, the rke2-selinux RPM is installed via the yum.yml task as part of rke2-common package when the tarballs are not present. I'd be curious to know why the maintainers of RKE2 do not package rke2-selinux with the air-gapped tarballs.

Closing this issue.

from rke2-ansible.