zalando / zalando/postgres-operator

Failed in-place upgrade to postgres 15

Open
#2,261 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question technical issue
Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

  • Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.9.0
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
  • Are you running Postgres Operator in production? No
  • Type of issue? Bug report

Hi,

I'm testing the in-place upgrade function from several versions and found that it does not upgrade to version 15, with 1.9.0 operator.

I trigger the upgrade by changing the version in the CRD and then I check the version by doing a select version from the master pod.

It worked for example from 13 to 14, or from 12 to 13, or even directly from 12 to 14, but if I try to run the upgrade from any version to 15 fails, showing no interesting log details

Operator log:

time="2023-03-07T16:25:38Z" level=error msg="major version upgrade failed: could not execute: command terminated with exit code 1" cluster-name=kleecks/kleecks-milano-p9dr-postgresql pkg=cluster

No problem performing the same operation with other versions

Thank you

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the upgrade by changing the PostgreSQL version in the CRD and checking the version from the master pod, comparing the failing upgrade to the reported successful upgrades. Start with the operator log showing the major version upgrade command failure. Done means an in-place upgrade to PostgreSQL 15 completes successfully and the master pod reports version 15.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, postgresql
Domain
databases, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.