-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5.5.1 broken upgrade #3868
Comments
hi @Elyytscha! Sorry to hear you are having trouble. Unfortunately the Additionally, I'll also reference the following GitHub issues for similar threads and conversations related to this:
Fortunately, you should be able to quickly get back up and running using the PG apiVersion: postgres-operator.crunchydata.com/v1beta1
kind: PostgresCluster
metadata:
name: hippo
spec:
backups:
pgbackrest:
image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.47-0
image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.10-0
... And from there you can perform a major PG upgrade to onto a supported version of PG using CPK's Major Postgres Version Upgrade functionality. |
thanks for the help, i will close didn't noticed that only the latest 2 postgres version are supported (it feels a little bit harsh to drop support in an upgrade from 5.5.0 -> 5.5.1 just saying) my 2 cents
kind: PostgresCluster
apiVersion: postgres-operator.crunchydata.com/v1beta1
metadata:
name: hippo
spec:
...
defaultPublicAccess: true
postgresVersion: 16
... which defaults to no with the actual behaviour, while true gives the default user access to the public schema |
Overview
autoupgrade to 5.5.1 (Mar 8, 2024, 4:17 PM UTC) broke my postgres
Environment
okd 4.14
Please provide the following details:
ubi8-5.x.y-0
)Steps to Reproduce
REPRO
Provide steps to get to the error condition:
EXPECTED
a working postgres instance
ACTUAL
Logs
Please provided appropriate log output or any configuration files that may help troubleshoot the issue. DO NOT include sensitive information, such as passwords.
Additional Information
Please provide any additional information that may be helpful.
The text was updated successfully, but these errors were encountered: