Skip to content

Resolve "Update Patroni to 3.0.1"

João Alexandre Cunha requested to merge 7415-update-patroni-to-3-0-1 into master

What does this MR do?

Bumps Patroni to 3.0.1.

Warning Notes from the Major version 3.0.0

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.

Removed feature from 2.1.6

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

✅ !6898 (comment 1406579317)

2. Provision minimal PG cluster and run QA against it - triggering RAT pipeline

✅ !6898 (comment 1406579317)

3. Replication

✅ !6898 (comment 1406579317)

4. Failover

✅ !6898 (comment 1406579317)

5. Backup / Restore

✅ !6898 (comment 1736909719)

6. Setup a Geo instance

✅ !6898 (comment 1747812500)

7. Upgrade from a previous Patroni 2.1.0 from a previous release to 16.0 to the new release with 3.0.1

✅ !6898 (comment 1733179755)

8. Upgrade from a standalone Postgres version to Patroni 3.0.1

✅ !6898 (comment 1783926852)

9. Upgrade Postgres version from v13 to v14 with Patroni 3.0.1

✅ !6898 (comment 1406579317)

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 or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
  • If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger: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, duration 10s, URI scheme://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)

Edited by Hossein Pursultani

Merge request reports