Bug #120424 CDN (AkamaiNetStorage) serves stale RPM for mysql84-community-release-el8-2 causing checksum mismatch with current prima

Description:
The repo.mysql.com delivers a stale RPM file whose SHA-256 checksum does not match the value declared in the current primary.xml metadata. This causes any repository manager that validates checksums to reject the file and fail synchronization entirely.

Timestamp evidence from HTTP headers:
- RPM file Last-Modified:   Tue, 08 Jul 2025 05:48:18 GMT  (Content-Length: 15440)
- repomd.xml Last-Modified: Fri, 24 Apr 2026 13:27:39 GMT

The metadata was updated in April 2026 referencing a new RPM, but the CDN still serves the old binary from July 2025.

How to repeat:
1. Download the RPM:
   wget http://repo.mysql.com/yum/mysql-8.4-community/el/8/x86_64/mysql84-community-release-el8-2....

2. Compute its checksum:
   sha256sum mysql84-community-release-el8-2.noarch.rpm
   Result: 84f0dc35dc197be1c9a1e604b7f7605619ee2b6b0e553efe3b74360ca651998b

3. Fetch primary.xml and grep for the package:
   curl -s http://repo.mysql.com/yum/mysql-8.4-community/el/8/x86_64/repodata/primary.xml.gz | zcat | grep -A3 'mysql84-community-release'
   Declared checksum: ff40f3fbeaa13204d20f9707865c6cfd656a1c3c4b9125286fbcc946a7f24892

4. Checksums do not match → sync tools reject the package.

Suggested fix:
Refresh primary.xml.gz file or refresh cache on Akamai CDN.

Acknowledged. Thanks for the bug report.

We have cleared the Akamai Cache. Please could you try now.

Working now — checksum is correct and sync completed without errors.

Thanks for fixing it so fast!