Fixes #31834 - Use PostgreSQL 12 on EL8#650
Conversation
ehelms
left a comment
ehelms
left a comment
There was a problem hiding this comment.
I'd like to see this available in the next Foreman release so that before Katello 4.0 goes GA EL8 installs are on PG 12 to avoid unnecessary upgrades for users.
|
Now that my PR is merged I've updated this to point to a specific git commit. theforeman/theforeman.org#1788 includes the upgrade instructions. |
|
For other reviewers: this is part of a larger change. I'd first like to get the upgrade instructions ready. We also don't want to break the upgrade pipelines so forklift needs to learn something too. |
|
I've got a PR over in FOC to automate this process to expand its availability to both Forklift and users: theforeman/foreman-operations-collection#21 |
|
I also found puppetlabs/puppetlabs-postgresql#1253 which at least was an issue on my own server. Maybe it's not a problem. It also looks like they're working on a 7.0.0 release which includes my fix. |
|
One complication is that this drops support for puppet 5 in metadata.json. Also looks like we'll need new module releases to allow version 7.x. |
|
That sounds like a lot of churn and change to take on in Foreman 2.4? As this is needed for Katello 4.0 to go GA. |
|
Honestly, given where Foreman 2.4 is and how much is involved here I'd say this is actually too late in the cycle. I'm starting to think we should push this to Katello 4.1. |
Then we would need to strongly advertise PostgreSQL 12 everywhere and make it clear PG 10 is not supported. Users will still end up with PG 10 without enforcement and then we have to upgrade them. I do not think Katello 4.0 should GA without enforcement of PG 12. Whether that is a version of this that works properly, or we use https://github.com/theforeman/foreman-installer/pull/646/files and update it in 4.1 to this method. This feels bad to start users out on the wrong foot who want to start with a clean EL8 or who start looking to migrate from EL7 to EL8. |
This aligns Red Hat 7 and Red Hat 8 on PostgreSQL 12. It uses the a specific git commit for DNF module support but without dropping Puppet 5 to allow for a cherry pick to 2.4. After develop drops Puppet 5 support, it should switch to >= 7.0.1 as a version specifyer. It may break existing installations on PostgreSQL 10 since there is no upgrade path. Those users are recommended to set version to 10 in their custom-hiera.yaml or upgrade to PostgreSQL 12.
|
I have switched it back to the specific commit ID we had previously. That allows us to not drop Puppet 5 and avoid the churn for 2.4. I do think we should soon change it to |
👍 |
|
Regardless of the approach we take in this PR, we still need to update forklift and our CI. Now that this has been merged, our upgrade pipelines will be broken. |
3 participants
This aligns Red Hat 7 and Red Hat 8 on PostgreSQL 12. It uses the branch manage_dnf_module.
It may break existing installations on PostgreSQL 10 since there is no upgrade path. Those users are recommended to set version to 10 in their custom-hiera.yaml.
This is an alternative to #646.