After postgresql restore, and deleting old backup from S3 container, postgresql/leader remains blocked with Move restored cluster to another S3 bucket

[nsakkos]

Steps to reproduce

1. Deploy postgresql charm, integrated with s3-integrator for backups and tls-certificates-operator
2. Create a backup with juju run postgres/0 create-backup
3. Remove postgresql application
4. Follow restore instructions
5. Once cluster is restored, postgresql is blocked with "the S3 repository has backups from another cluster".
6. Following instructions here, clean the container

Expected behavior

I expected the charm to detect that the container was now empty, become unblocked, and allow me to re-use the container for new backups.

Actual behavior

postgresql/leader remained in blocked status with message Move restored cluster to another S3 bucket. I tried restarting the jujud system service and restarting the VM, but the unit remained blocked. The only solution was to create a new bucket.

juju status: https://pastebin.canonical.com/p/X23QQnGJW6/

Versions

Operating system: Ubuntu 22.04.5 LTS

Juju CLI: 3.5.5-ubuntu-amd64

Juju agent: 3.5.5

Charm revision: postgresql 14/stable 468

Log output

Juju debug log: https://pastebin.canonical.com/p/jMVZ6JTtZx/

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-6399.

This message was autogenerated