Skip to content

fix(roles/repo_proxysql): use the AlmaLinux builds where no CentOS build exists - #506

Merged
NavidSassan merged 2 commits into
mainfrom
fix/repo-proxysql-el8-3.0
Oct 27, 2026
Merged

NavidSassan merged 2 commits into
mainfrom
fix/repo-proxysql-el8-3.0

Conversation

@NavidSassan

Copy link
Copy Markdown
Member

repo.proxysql.com has no centos/8 for 3.0 and no centos/9 for 2.4/2.5, so those combinations failed with a 404. The repo file now uses almalinux/ exactly where centos/ does not exist; every combination that worked before renders the same URL.

  • The EL 8 builds of 3.0 (which lag behind, 3.0.9 vs. 3.0.11) need openssl3-libs from EPEL. The proxysql playbook now runs repo_baseos (CRB on Rocky 9+) and repo_epel, with proxysql__skip_repo_baseos / proxysql__skip_repo_epel.
  • The mirror baseurl was copied from repo_opensearch and never matched; it now follows the upstream path (<mirror>/ProxySQL/proxysql-<version>.x/<centos|almalinux>/$releasever). No ProxySQL mirror exists yet, so nothing breaks.
  • README example and availability list include 3.0; COMPATIBILITY.md: RHEL 10 tested (3.0 only).

Tested with the role on Rocky 8, 9 and 10 containers (dnf makecache for 2.2 to 3.0, dnf install with gpgcheck), and the playbook repo tags on Rocky 8/9: 3.0.9 installs on EL 8 with EPEL, 3.0.11 on EL 9.

NavidSassan and others added 2 commits October 27, 2026 16:11
…ild exists

3.0 has no centos/8 and 2.4/2.5 have no centos/9 on repo.proxysql.com.
The EL 8 builds of 3.0 need openssl3-libs from EPEL, so the proxysql
playbook deploys repo_baseos (CRB) and repo_epel. The mirror baseurl was
copied from repo_opensearch and now follows the upstream path. Verified
with dnf on Rocky 8, 9 and 10.
@NavidSassan
NavidSassan merged commit 6f01669 into main Oct 27, 2026
13 checks passed
@NavidSassan
NavidSassan deleted the fix/repo-proxysql-el8-3.0 branch October 27, 2026 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant