Description:
We have installed Percona operator 2.8.2 with pgbackrest image
[root@bastion-node pg-db]# oc describe pod pg-cluster-sa-pg-db-backup-9xd8-p8qvz
Events:
Type Reason Age From Message
Normal Scheduled 8m35s default-scheduler Successfully assigned percona/pg-cluster-sa-pg-db-backup-9xd8-p8qvz to tmo-cb-5.lab.idso.lan
Warning Failed 6m54s (x8 over 8m32s) kubelet Error: container create failed: executable file /usr/local/bin/init-entrypoint.sh not found in $PATH: No such file or directory
Normal Pulling 6m41s (x9 over 8m34s) kubelet Pulling image “registry.connect.redhat.com/percona/percona-postgresql-operator-containers:2.8.2-ppg-16-pgbackrest”
Normal Pulled 3m32s (x12 over 6m21s) kubelet (combined from similar events): Successfully pulled image “registry.connect.redhat.com/percona/percona-postgresql-operator-containers:2.8.2-ppg-16-pgbackrest” in 2.494s (2.494s including waiting). Image size: 433225130 bytes.
According to information available online, the pgbackrest RedHat image is experiencing issues, and even when using the Docker image, the same error occurs.
Tried creating the error mount with config maps it was of no use. Expecting some guidance to mitigate the issue.
Steps to Reproduce:
[Step-by-step instructions on how to reproduce the issue, including any specific settings or configurations]
Version:
percona-postgresql-operator:2.8.2-postgres-operator
percona-postgresql-operator-containers:2.8.2-ppg-16-pgbackrest
percona-postgresql-operator-containers:2.8.2-ppg-16-postgres
Logs:
Appended the log error and attached the values.yaml of charts/pg-db
Expected Result:
[What the user expected to see or happen before the issue occurred]
Actual Result:
[What actually happened when the user encountered the issue]
Additional Information:
[Include any additional information that could be helpful to diagnose the issue, such as browser or device information]