After upgrading to 2.5.0, scheduled backups’ pg-backup objects ends up stuck in “Running” status, leading to subsequent backups being blocked.
Even though the backup pods were completed.
From:
Then using a schedule
Then tuning
then upgrading
Then upgrading images to 2.5.0 in the perconapgclusters object
=> no apparent issues yet
After a few backups, it got stuck at running as well.
Trying to delete pg-backup, backup pods, and removing annotations led to issues with the leftovers still blocking the subsequent backups
Backups just pile up after that
After upgrading to 2.5.0, scheduled backups’ pg-backup objects ends up stuck in “Running” status, leading to subsequent backups being blocked.
Even though the backup pods were completed.
How I reproduced:
From:
Then using a schedule
Then tuning
then upgrading
Then upgrading images to 2.5.0 in the perconapgclusters object
=> no apparent issues yet
After a few backups, it got stuck at running as well.
Trying to delete pg-backup, backup pods, and removing annotations led to issues with the leftovers still blocking the subsequent backups
Backups just pile up after that