Missing RPM packages in the CentOS 8 aarch64 RPM repository

[chamarakera]

Describe the bug:

Yesterday(28/01/2025), I installed RKE2 version v1.30.8+rke2r1 using the https://rpm.rancher.io/rke2/stable/1.30/centos/8/aarch64 repo on my AL2023 instance. But today (29/01/2025), when I checked the same repo, only the RPM for v1.30.9+rke2r1 version is available.

However, when I list packages in the x86_64 repo https://rpm.rancher.io/rke2/stable/1.30/centos/8/x86_64, I can see RPM packages for older versions of RKE2 as well.

I noticed the same behavior for other versions like 1.29, 1.31, and 1.32. Each aarch64 repo only contains the latest released version of the RPM. The same applies to the rke2-agent packages as well.

Steps To Reproduce:

$ uname -a
Linux 6.1.124-134.200.amzn2023.aarch64 #1 SMP Tue Jan 14 08:15:20 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

$ cat /etc/yum.repos.d/rancher-rke2.repo
[rancher-rke2-1.30-stable-x86_64]
name=Rancher RKE2 1.30 (stable)
baseurl=https://rpm.rancher.io/rke2/stable/1.30/centos/8/x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=0
gpgkey=https://rpm.rancher.io/public.key
[rancher-rke2-1.30-stable-aarch64]
name=Rancher RKE2 1.30 (stable)
baseurl=https://rpm.rancher.io/rke2/stable/1.30/centos/8/aarch64
enabled=1
gpgcheck=1
repo_gpgcheck=0
gpgkey=https://rpm.rancher.io/public.key

$ yum search rke2-agent --showduplicates
rke2-agent-1.30.0~rke2r1-0.el8.x86_64 : RKE2 Agent
rke2-agent-1.30.1~rke2r1-0.el8.x86_64 : RKE2 Agent
rke2-agent-1.30.2~rke2r1-0.el8.x86_64 : RKE2 Agent
rke2-agent-1.30.3~rke2r1-0.el8.x86_64 : RKE2 Agent
rke2-agent-1.30.4~rke2r1-0.el8.x86_64 : RKE2 Agent
rke2-agent-1.30.5~rke2r1-0.el8.x86_64 : RKE2 Agent
rke2-agent-1.30.6~rke2r1-0.el8.x86_64 : RKE2 Agent
rke2-agent-1.30.7~rke2r1-0.el8.x86_64 : RKE2 Agent
rke2-agent-1.30.8~rke2r1-0.el8.x86_64 : RKE2 Agent
rke2-agent-1.30.9~rke2r1-0.el8.x86_64 : RKE2 Agent
rke2-agent-1.30.9~rke2r1-0.el8.aarch64 : RKE2 Agent

Expected behavior:

The aarch64 repo should also retain older versions of the RPM to ensure backward compatibility and avoid issues with new nodes joining the cluster due to older RPMs being replaced by newer versions.

[dereknola]

This is a known issue, closing as duplicate of #7174