CLOS-2132: Add PGDG PostgreSQL vendor PES events and pgdg96/pgdg10 mappings, migrate EOL versions#27
Open
prilr wants to merge 2 commits into
Conversation
…ppings
The PostgreSQL PGDG vendor files had an empty postgresql_pes.json (no
package events) and were missing repo mappings for pgdg96 and pgdg10.
Without PES events, Leapp treats PGDG packages as unknown and can
silently drop them or leave them broken after upgrade; without the
pgdg96/pgdg10 mappings, customers running those PGDG versions on CL7
have no Leapp-known target on CL8.
Populated postgresql_pes.json with 52 action=6 (Moved) events covering
the core packages (postgresql<N>, postgresql<N>-server,
postgresql<N>-libs, postgresql<N>-contrib) for:
CL7 -> CL8: postgresql{96,10,11,12,13,14,15}
CL8 -> CL9: postgresql{11,12,13,14,15,16}
Added pgdg96 and pgdg10 source repo entries plus el8-pgdg96 and
el8-pgdg10 target repo stanzas. Target URLs use the PGDG yum-archive
host (consistent with the existing el8-pgdg11 stanza for EOL versions).
PES event IDs 22777-22828 do not collide with existing IDs across all
PES files (verified by tests/validate_ids.py). os_name values use
CentOS / AlmaLinux to match the convention in the other vendor PES
files (mariadb, nginx, etc.); the field is ignored at runtime by
parse_release(), which only uses major/minor versions.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
PostgreSQL 12 (EOL 2024-11) and PostgreSQL 13 (EOL 2025-11) have been
removed from the live PGDG repository host. Requests to the
download.postgresql.org URLs in postgresql.repo.{el8,el9} now return
HTTP 410 Gone, which would break leapp upgrades for any customer whose
source system has these repos enabled:
download.postgresql.org/pub/repos/yum/{12,13}/redhat/rhel-{8,9}-...
-> 410 Gone
yum-archive.postgresql.org/{12,13}/redhat/rhel-{8,9}-...
-> 200 OK
Move the four baseurl lines (pgdg12 and pgdg13 in both .el8 and .el9)
to the archive host, consistent with the existing treatment of pgdg11
(EOL 2023-11, already on archive) and pgdg9.6/pgdg10 (EOL 2021-11 /
2022-11, also archive).
Discovered while validating the pgdg96/pgdg10 URLs added by the
previous commit on this branch; the live-vs-archive split is the same
pattern PGDG applies to every EOL major version once it stops shipping
patches.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The PostgreSQL PGDG vendor files had an empty postgresql_pes.json (no package events) and were missing repo mappings for pgdg96 and pgdg10.
Without PES events, Leapp treats PGDG packages as unknown and can silently drop them or leave them broken after upgrade; without the pgdg96/pgdg10 mappings, customers running those PGDG versions on CL7 have no Leapp-known target on CL8.
Populated postgresql_pes.json with 52 action=6 (MOVED) events covering the core packages (postgresql, postgresql-server, postgresql-libs, postgresql-contrib) for:
CL7 -> CL8: postgresql{96,10,11,12,13,14,15}
CL8 -> CL9: postgresql{11,12,13,14,15,16}
Added pgdg96 and pgdg10 source repo entries plus el8-pgdg96 and el8-pgdg10 target repo stanzas. Target URLs use the PGDG yum-archive host (consistent with the existing el8-pgdg11 stanza for EOL versions).
In addition, moved the EOL versions to the yum-archive URLs, as they are no longer accessible from the links currently stored in the leapp-data repofile configs.
os_name values use CentOS / AlmaLinux to match the convention in the other vendor PES files; the field is ignored at runtime by parse_release(), which only uses major/minor versions.