Bug: MaxScale 'latest' repository symlink returns 404 Not Found (dlm.mariadb.com)

Description:

When configuring the MariaDB Foundation repository using the official mariadb_repo_setup script with default arguments, the repository configuration for MariaDB MaxScale points to a broken latest symlink, causing dnf package manager operations to fail with a 404 error.

Environment:

• OS: AlmaLinux 8.10 (RHEL 8 clone)
• Setup Method: mariadb_repo_setup script (per the official documentation)

Steps to Reproduce:

Run the repository setup script with default parameters:

bash ./mariadb_repo_setup 

Attempt to install the maxscale package (or run dnf update):

dnf install maxscale

Expected Behavior:

The script configures the MaxScale repository, and the latest path correctly resolves to the newest stable release, allowing the package to install successfully.

Actual Behavior:

The installation fails during metadata generation because the latest URL path is broken and returns a 404 Status Code:

MariaDB Server                                                 420 kB/s | 862 kB     00:02    

MariaDB MaxScale                                               1.6 kB/s | 109  B     00:00    

Errors during downloading metadata for repository 'mariadb-maxscale':

  - Status code: 404 for https://dlm.mariadb.com/repo/maxscale/latest/yum/rhel/8/x86_64/repodata/repomd.xml (IP: 104.17.191.14)

Error: Failed to download metadata for repo 'mariadb-maxscale': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

Workaround:

Explicitly defining the MaxScale version during repository setup bypasses the broken latest symlink and works perfectly. For example:

bash ./mariadb_repo_setup --mariadb-maxscale-version="24.02"

Could the infrastructure team please check why https://dlm.mariadb.com/repo/maxscale/latest is no longer resolving?

Thank you!