Closed javierdelapuente closed 8 months ago
Hi @javierdelapuente! Have you reset the passwords as according the instructions from https://charmhub.io/postgresql-k8s/docs/h-migrate-cluster-via-restore?
Hi @marceloneppel, yes, the password was reset.
Thanks @javierdelapuente! The fix has been published through revision 185 in the 14/edge
channel.
Steps to reproduce
Backup database to a S3 bucket.
Create a new different cluster. Same controller and model names as in the previous one.
juju deploy postgresql-k8s --trust
juju deploy s3-integrator
juju run s3-integrator/leader sync-s3-credentials access-key= secret-key=
juju config s3-integrator .... (same as in the original cluster)
juju relate s3-integrator postgresql-k8s At this point, with s3 correctly configured, the workload gets into
blocked
state with messagefailed to initialize stanza, check your S3 settings
juju run postgresql-k8s/leader list-backups Backups are correctly shown.
juju run postgresql-k8s/leader restore backup-id=2023-11-27T09:37:51Z Fails to restore backups, as the charm does not expect the current block state.
Expected behavior
The backup should be restored in the new cluster.
Actual behavior
Versions
Operating system: Ubuntu 22.04.3 LTS
Juju CLI: 3.1.6-genericlinux-amd64
Juju agent:
Charm revision:
microk8s: MicroK8s v1.27.7 revision 6101
Log output
Juju debug log:
When creating the integration:
When trying to restore:
Additional context
Changing the line https://github.com/canonical/postgresql-k8s-operator/blob/f1a470ddabe8ea7acc5e7407c8753c1d2273961a/src/backups.py#L639C11-L639C11 to allow the current message I manage to restore the database successfully.