Please ensure you do the following when reporting a bug:

• Provide a concise description of what the bug is.
• Provide information about your environment.
• Provide clear steps to reproduce the bug.
• Attach applicable logs. Please do not attach screenshots showing logs unless you are unable to copy and paste the log data.
• Ensure any code / output examples are properly formatted for legibility.

Note that some logs needed to troubleshoot may be found in the /pgdata/<CLUSTERNAME>/pg_log directory on your Postgres instance.

An incomplete bug report can lead to delays in resolving the issue or the closing of a ticket, so please be as detailed as possible.

If you are looking for general support, please view the support page for where you can ask questions.

Thanks for reporting the issue, we're looking forward to helping you!

Overview

There is internal.percona.com/delete-restore finalizer on pg-restore cr after restore completion.
In cluster deprovision, we have to modify the CR and delete the finalizer, otherwise the cr hangs in a "terminating" state.

Environment

Please provide the following details:

• Platform: clusters on AWS, AKS
• Platform Version: (e.g. 1.20.3, 4.7.0)
• PGO Image Tag: (e.g. ubi8-5.x.y-0)
• Postgres Version : 16
• Storage: (e.g. hostpath, nfs, or the name of your storage class)

Steps to Reproduce

REPRO

Provide steps to get to the error condition:

1. Create a pg cluster (16)
2. Create a backup on s3, or azure storage
3. Try to create a restore form the backup
4. Delete the pg cluster

EXPECTED

1. After the restore completion I expect to remove the internal.percona.com/delete-restore finalizer

ACTUAL

1. After the restore completion the internal.percona.com/delete-restore finalizer exists on pg-restore cr

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.