Yum/dnf update fails with HTTP 404 from AlmaLinux 9.7 repositories on CloudLinux 9

Issue

yum or dnf operations fail on a CloudLinux 9 server because AlmaLinux 9.7 repository metadata or package files return HTTP 404 errors.

The issue may appear during yum update, yum upgrade, dnf makecache, or kernel status checks that call /usr/bin/yum.

Example errors:

Errors during downloading metadata for repository 'appstream':
  - Status code: 404 for http://vault.almalinux.org/9.7/AppStream/x86_64/os/repodata/...

Error: Failed to download metadata for repo 'appstream': Yum repo downloading error:
Downloading error(s): repodata/... - Cannot download, all mirrors were already tried without success

The error may also affect BaseOS package downloads, for example:

[MIRROR] package-name.el9_7.x86_64.rpm: Status code: 404 for http://vault.almalinux.org/9.7/BaseOS/x86_64/os/Packages/...
[FAILED] package-name.el9_7.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success

Environment

• AlmaLinux 9.7
• CloudLinux OS 9
• yum / dnf
• Affected repositories may include:
  • appstream
  • baseos
  • crb
  • devel
• cloudlinux-release package may be outdated

Solution

The issue is resolved, and you should be able to update your system successfully now.

---

Temporary Solution

1. Update the cloudlinux-release package while excluding the affected AlmaLinux repositories:

dnf update cloudlinux-release --disablerepo=appstream*,baseos*,crb*,devel* --enablerepo=cl*

2. Clean the metadata cache:

dnf clean metadata

3. Rebuild the metadata cache:

dnf makecache --refresh

4. Retry the system update:

dnf update

5. If the update proceeds normally, let the customer continue with the package transaction.
6. If cloudlinux-release cannot be updated through dnf, check the latest available cloudlinux-release package in the CloudLinux repository and update it manually from the official CloudLinux repository. After that, run:

dnf clean metadata
dnf makecache --refresh
dnf update

Note: Do not leave AlmaLinux BaseOS/AppStream/CRB/Devel repositories permanently disabled. Disabling the affected repositories may allow unrelated packages to update temporarily, but it should not be treated as a permanent solution on CloudLinux 9 systems.

Cause

The affected CloudLinux 9 systems were still using AlmaLinux 9.7 repository metadata or package paths that returned HTTP 404 errors. As a result, yum/dnf could not download the required repository metadata or packages, and the update process stopped.

The issue was addressed by the packaging team under CLPKG-1219. Updating cloudlinux-release applies the corrected repository configuration and allows metadata generation and package updates to proceed normally.

Useful Links

Internal Jira task: CLPKG-1219