All postgresql pods do not restart on restarting the database
Description
Environment
Attachments
is caused by
relates to
Activity
Edith Erika Puclla Pareja September 11, 2024 at 9:55 AM
Hi now I tested in version 1.2.0 and it works fine, all pods are restarting after resume the database from the GUI
Edith Erika Puclla Pareja September 3, 2024 at 4:04 PM
Hi , @Manish Chawla. I am testing this again. I created several databases on Percona Everest and I restarted all of them. I don't see any pod that gets stuck now. Let me know If I should test it in another way.
Version tested: v1.2.0-rc1
Manish Chawla August 26, 2024 at 8:48 AM
Thanks Diogo, I am closing this issue as the repo host pod issue will be resolved in .
Diogo Recharte August 20, 2024 at 10:51 AM
Nonetheless, I created another ticket for the PGOperator to fix this harmless but incorrect behavior.
Diogo Recharte August 20, 2024 at 9:32 AM
Hi Manish, please recall my old comment in this ticket:
I also confirmed that there is no real impact of having the repo-host pod not restarting. Even though the current behavior is incorrect, given that this doesn’t really impact the restart functionality (the important bit is that the engine pods are restarted)
I think we can move this ticket to done
Tested with Everest vv0.0.0-74fd87c version.
Create a postgresql database of 3 nodes, with external access enabled.
Add some data and then take a manual backup.
After the manual backup completes, Suspend and Resume the database. The database gets paused after Suspend comes up successfully after Resume.
Pod status
Restart the database. All the pods do not restart
From the above, the pods
postgresql-283-instance1-69xx-0andpostgresql-283-repo-host-0do not restart and remain inRunningstatus.The postgresql-283-instance1-69xx-0 pod displays this log
Logs attached for postgres operator, everest operator, postgresql-283-instance1-69xx-0 pod, postgresql-283-repo-host-0.