Resolve "Update Patroni to 3.0.1"
What does this MR do?
Bumps Patroni to 3.0.1.
3.0.0
Warning Notes from the Major version As per https://patroni.readthedocs.io/en/latest/releases.html#version-3-0-0:
Version 3.0.0 is the last release supporting Python 2.7.
Upcoming release will drop support of Python versions older than 3.7.
The RAFT support is deprecated. We will do our best to maintain it, but take neither guarantee nor responsibility for possible issues. This version is the first step in getting rid of the “master”, in favor of “primary”. Upgrading to the next major release will work reliably only if you run at least 3.0.0.
...
Removed functionality
Remove patronictl scaffold (Alexander Kukushkin)
The only reason for having it was a hacky way of running standby clusters.
2.1.6
Removed feature from Remove patronictl configure (Polina Bungina)
There is no more need for a separate patronictl config creation.
Test Scenarios
1. Verify existing Patroni commands work as expected
2. Provision minimal PG cluster and run QA against it - triggering RAT pipeline
3. Replication
4. Failover
5. Backup / Restore
6. Setup a Geo instance
7. Upgrade from a previous Patroni 2.1.0 from a previous release to 16.0 to the new release with 3.0.1
8. Upgrade from a standalone Postgres version to Patroni 3.0.1
9. Upgrade Postgres version from v13 to v14 with Patroni 3.0.1
Related issues
Update Patroni to 3.0.1 (#7415 - closed)
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion.
Required
-
MR title and description are up to date, accurate, and descriptive. -
MR targeting the appropriate branch. -
Latest Merge Result pipeline is green. -
When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.
For GitLab team members
If you don't have access to this, the reviewer should trigger these jobs for you during the review process.
-
The manual Trigger:ee-package
jobs have a green pipeline running against latest commit. -
If config/software
orconfig/patches
directories are changed, make sure thebuild-package-on-all-os
job within theTrigger:ee-package
downstream pipeline succeeded. -
If you are changing anything SSL related, then the Trigger:package:fips
manual job within theTrigger:ee-package
downstream pipeline must succeed. -
If CI configuration is changed, the branch must be pushed to dev.gitlab.org
to confirm regular branch builds aren't broken.
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes. -
Documentation created/updated. -
Tests added. -
Integration tests added to GitLab QA. -
Equivalent MR/issue for the GitLab Chart opened. -
Validate potential values for new configuration settings. Formats such as integer 10
, duration10s
, URIscheme://user:passwd@host:port
may require quotation or other special handling when rendered in a template and written to a configuration file.
Closes #7415 (closed)