From the above, the pods postgresql-283-instance1-69xx-0 and postgresql-283-repo-host-0 do not restart and remain in Running status.
The postgresql-283-instance1-69xx-0 pod displays this log
2024-01-22 13:13:43,079 INFO: no action. I am (postgresql-283-instance1-69xx-0), the leader with the lock
2024-01-22 13:13:53,079 INFO: no action. I am (postgresql-283-instance1-69xx-0), the leader with the lock
2024-01-22 13:14:03,083 INFO: no action. I am (postgresql-283-instance1-69xx-0), the leader with the lock
2024-01-22 13:14:13,080 INFO: no action. I am (postgresql-283-instance1-69xx-0), the leader with the lock
Logs attached for postgres operator, everest operator, postgresql-283-instance1-69xx-0 pod, postgresql-283-repo-host-0.
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
kubectl get pods -n percona-everest NAME READY STATUS RESTARTS AGE everest-operator-controller-manager-c9d46f46d-7gzjf 2/2 Running 0 120m mysql-ueo-haproxy-0 2/2 Running 0 67m mysql-ueo-pxc-0 1/1 Running 0 67m percona-everest-8766d575c-r854w 1/1 Running 0 6h8m percona-postgresql-operator-7d97dfb6b7-8wntj 1/1 Running 0 3h47m percona-server-mongodb-operator-7695c6654d-hh8df 1/1 Running 0 6h9m percona-xtradb-cluster-operator-f9485b967-z2kvp 1/1 Running 0 121m pg-client-19910 1/1 Running 0 145m postgresql-283-backup-cql5-smt6f 0/1 Completed 0 169m postgresql-283-backup-z6r5-bvpbk 0/1 Completed 0 3h19m postgresql-283-instance1-42z5-0 4/4 Running 0 142m postgresql-283-instance1-69xx-0 4/4 Running 0 147m postgresql-283-instance1-fsmb-0 4/4 Running 0 142m postgresql-283-pgbouncer-c59d468c8-2sqrp 2/2 Running 0 142m postgresql-283-pgbouncer-c59d468c8-4rssm 2/2 Running 0 142m postgresql-283-pgbouncer-c59d468c8-d4ncb 2/2 Running 0 142m postgresql-283-repo-host-0 2/2 Running 0 147m restored-postgresql-28-backup-h4rt-4fclt 0/1 Completed 0 151m xb-cron-mysql-ueo-s3-202412210408-1kh4f-7zrl4 0/1 Completed 0 54m xb-cron-mysql-ueo-s3-202412210408-1kh4f-qp84d 0/1 Error 0 54m xb-cron-mysql-vu8-s3-202412210047-6oioo-7fwvr 0/1 Completed 0 94m
Restart the database. All the pods do not restart
kubectl get pods -n percona-everest NAME READY STATUS RESTARTS AGE everest-operator-controller-manager-c9d46f46d-7gzjf 2/2 Running 0 121m mysql-ueo-haproxy-0 2/2 Running 0 68m mysql-ueo-pxc-0 1/1 Running 0 68m percona-everest-8766d575c-r854w 1/1 Running 0 6h8m percona-postgresql-operator-7d97dfb6b7-8wntj 1/1 Running 0 3h48m percona-server-mongodb-operator-7695c6654d-hh8df 1/1 Running 0 6h9m percona-xtradb-cluster-operator-f9485b967-z2kvp 1/1 Running 0 121m pg-client-19910 1/1 Running 0 145m postgresql-283-backup-cql5-smt6f 0/1 Completed 0 169m postgresql-283-backup-z6r5-bvpbk 0/1 Completed 0 3h19m postgresql-283-instance1-42z5-0 0/4 Init:0/2 0 1s postgresql-283-instance1-69xx-0 4/4 Running 0 148m postgresql-283-instance1-fsmb-0 0/4 Init:0/2 0 1s postgresql-283-pgbouncer-c59d468c8-87dxw 2/2 Running 0 2s postgresql-283-pgbouncer-c59d468c8-8t9kg 0/2 ContainerCreating 0 2s postgresql-283-pgbouncer-c59d468c8-cdss7 0/2 ContainerCreating 0 2s postgresql-283-repo-host-0 2/2 Running 0 148m restored-postgresql-28-backup-h4rt-4fclt 0/1 Completed 0 151m xb-cron-mysql-ueo-s3-202412210408-1kh4f-7zrl4 0/1 Completed 0 54m xb-cron-mysql-ueo-s3-202412210408-1kh4f-qp84d 0/1 Error 0 55m xb-cron-mysql-vu8-s3-202412210047-6oioo-7fwvr 0/1 Completed 0 94m kubectl get pods -n percona-everest NAME READY STATUS RESTARTS AGE everest-operator-controller-manager-c9d46f46d-7gzjf 2/2 Running 0 121m mysql-ueo-haproxy-0 2/2 Running 0 68m mysql-ueo-pxc-0 1/1 Running 0 68m percona-everest-8766d575c-r854w 1/1 Running 0 6h8m percona-postgresql-operator-7d97dfb6b7-8wntj 1/1 Running 0 3h48m percona-server-mongodb-operator-7695c6654d-hh8df 1/1 Running 0 6h9m percona-xtradb-cluster-operator-f9485b967-z2kvp 1/1 Running 0 121m pg-client-19910 1/1 Running 0 146m postgresql-283-backup-cql5-smt6f 0/1 Completed 0 169m postgresql-283-backup-z6r5-bvpbk 0/1 Completed 0 3h19m postgresql-283-instance1-42z5-0 0/4 Init:0/2 0 8s postgresql-283-instance1-69xx-0 4/4 Running 0 148m postgresql-283-instance1-fsmb-0 0/4 PodInitializing 0 8s postgresql-283-pgbouncer-c59d468c8-87dxw 2/2 Running 0 9s postgresql-283-pgbouncer-c59d468c8-8t9kg 2/2 Running 0 9s postgresql-283-pgbouncer-c59d468c8-cdss7 2/2 Running 0 9s postgresql-283-repo-host-0 2/2 Running 0 148m restored-postgresql-28-backup-h4rt-4fclt 0/1 Completed 0 151m xb-cron-mysql-ueo-s3-202412210408-1kh4f-7zrl4 0/1 Completed 0 55m xb-cron-mysql-ueo-s3-202412210408-1kh4f-qp84d 0/1 Error 0 55m xb-cron-mysql-vu8-s3-202412210047-6oioo-7fwvr 0/1 Completed 0 94m kubectl get pods -n percona-everest NAME READY STATUS RESTARTS AGE everest-operator-controller-manager-c9d46f46d-7gzjf 2/2 Running 0 121m mysql-ueo-haproxy-0 2/2 Running 0 68m mysql-ueo-pxc-0 1/1 Running 0 68m percona-everest-8766d575c-r854w 1/1 Running 0 6h9m percona-postgresql-operator-7d97dfb6b7-8wntj 1/1 Running 0 3h48m percona-server-mongodb-operator-7695c6654d-hh8df 1/1 Running 0 6h9m percona-xtradb-cluster-operator-f9485b967-z2kvp 1/1 Running 0 121m pg-client-19910 1/1 Running 0 146m postgresql-283-backup-cql5-smt6f 0/1 Completed 0 170m postgresql-283-backup-z6r5-bvpbk 0/1 Completed 0 3h19m postgresql-283-instance1-42z5-0 4/4 Running 0 19s postgresql-283-instance1-69xx-0 4/4 Running 0 148m postgresql-283-instance1-fsmb-0 4/4 Running 0 19s postgresql-283-pgbouncer-c59d468c8-87dxw 2/2 Running 0 20s postgresql-283-pgbouncer-c59d468c8-8t9kg 2/2 Running 0 20s postgresql-283-pgbouncer-c59d468c8-cdss7 2/2 Running 0 20s postgresql-283-repo-host-0 2/2 Running 0 148m restored-postgresql-28-backup-h4rt-4fclt 0/1 Completed 0 151m xb-cron-mysql-ueo-s3-202412210408-1kh4f-7zrl4 0/1 Completed 0 55m xb-cron-mysql-ueo-s3-202412210408-1kh4f-qp84d 0/1 Error 0 55m xb-cron-mysql-vu8-s3-202412210047-6oioo-7fwvr 0/1 Completed 0 95m
From the above, the pods
postgresql-283-instance1-69xx-0
andpostgresql-283-repo-host-0
do not restart and remain inRunning
status.The postgresql-283-instance1-69xx-0 pod displays this log
2024-01-22 13:13:43,079 INFO: no action. I am (postgresql-283-instance1-69xx-0), the leader with the lock 2024-01-22 13:13:53,079 INFO: no action. I am (postgresql-283-instance1-69xx-0), the leader with the lock 2024-01-22 13:14:03,083 INFO: no action. I am (postgresql-283-instance1-69xx-0), the leader with the lock 2024-01-22 13:14:13,080 INFO: no action. I am (postgresql-283-instance1-69xx-0), the leader with the lock
Logs attached for postgres operator, everest operator, postgresql-283-instance1-69xx-0 pod, postgresql-283-repo-host-0.