rpm.rancher.io RHEL 9 packages missing/removed

[taylortails]

Environmental Info:
K3s Version:
v1.29.5+k3s1

Node(s) CPU architecture, OS, and Version:
RHEL 9

Describe the bug:
Install fails on RHEL 9

Steps To Reproduce:

bash-5.1# curl -sfL https://get.k3s.io | sh -

Expected behavior:
install success

Actual behavior:

bash-5.1# curl -sfL https://get.k3s.io | sh -
[INFO]  Finding release for channel stable
[INFO]  Using v1.29.5+k3s1 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.29.5+k3s1/sha256sum-amd64.txt
[INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.29.5+k3s1/k3s
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Finding available k3s-selinux versions
Error: No matching Packages to list
Updating Subscription Management repositories.
Last metadata expiration check: 0:00:03 ago on Thu 20 Jun 2024 08:59:00 AM UTC.
Package k3s-selinux-1.5-1.el9.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[ERROR]  Failed to apply container_runtime_exec_t to /usr/local/bin/k3s, please install:
    dnf install -y container-selinux
    dnf install -y https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/

Additional context / logs:

bash-5.1# dnf install -y https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/
Updating Subscription Management repositories.
Last metadata expiration check: 0:02:49 ago on Thu 20 Jun 2024 08:49:55 AM UTC.
[MIRROR] : Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 104.21.2.160)
[MIRROR] : Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 104.21.2.160)
[MIRROR] : Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 104.21.2.160)
[MIRROR] : Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 104.21.2.160)
[FAILED] : Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 104.21.2.160)
Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 104.21.2.160)

[taylortails]

dnf install -y https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/
Updating Subscription Management repositories.
Last metadata expiration check: 0:18:20 ago on Wed 26 Jun 2024 10:42:30 AM UTC.
[MIRROR] : Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 172.67.129.95)
[MIRROR] : Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 172.67.129.95)
[MIRROR] : Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 172.67.129.95)
[MIRROR] : Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 172.67.129.95)
[FAILED] : Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 172.67.129.95)
Status code: 404 for https://rpm.rancher.io/k3s/stable/common/centos/9/noarch/ (IP: 172.67.129.95)

[brandond]

Nothing is missing. I see how the command suggested by the install script could be confusing since it appears to be missing the specific RPM to install, but since it's missing the file portion of the URL, the message is expected since you can't install the provided URL, which is a directory index and not a package.

You apparently have k3s-selinux-1.5-1.el9.noarch installed already, but the chcon -u system_u -r object_r -t container_runtime_exec_t /usr/local/bin/k3s command is failing for some reason, which is why the script suggests installing the package. Why is this command failing?

[taylortails]

chcon -u system_u -r object_r -t container_runtime_exec_t /usr/local/bin/k3s
chcon: failed to change context of '/usr/local/bin/k3s' to ‘system_u:object_r:container_runtime_exec_t:s0’: Invalid argument

Thanks for the steer... I'll try dig my end.

[bck01215]

Also having this issue. @taylortails did you find a solution?

[taylortails]

The machine state had become broken because of a mixture of dnf repos added when attempting to fix dependency issues, reverting to clean snapshot fixed the issue. @bck01215