Hi All,
I’m using operator 1.3.0 successfully including the backups to S3 working perfectly.
However with the new 1.4.1 operator the backups no longer work. If I use the exact same YAMLs on operator 1.3.0 everything is successful.
Here is what I did:
As always I created the S3 secret like this:
apiVersion: v1
kind: Secret
metadata:
name: op140tst-clu-backrest-repo-config
type: Opaque
data:
aws-s3-key:
aws-s3-key-secret:
This is my cr backup section:
backup:
image: percona/percona-postgresql-operator:1.4.0-ppg14-pgbackrest-repo@sha256:5ca47c5c6ddd85aa47b6a2e3e618a731804583d838900a8287ff0a821e158645
backrestRepoImage: percona/percona-postgresql-operator:1.4.0-ppg14-pgbackrest-repo@sha256:5ca47c5c6ddd85aa47b6a2e3e618a731804583d838900a8287ff0a821e158645
resources:
requests:
cpu: 300m
memory: “48Mi”
limits:
cpu: 500m
memory: “128Mi”
affinity:
antiAffinityType: preferred
volumeSpec:
size: 1G
accessmode: ReadWriteOnce
storagetype: dynamic
storageclass: “”
storages:
cephs3:
bucket: pgsql-op140tst-postgresql-dev-eu-at-3
endpointUrl:
uriStyle: “path”
region: “us-east-1”
verifyTLS: false
type: “s3”
schedule:
- name: “daily-full-backup”
schedule: “7 12 * * *”
keep: 15
type: full
storage: “cephs3”
Everything looks successful, but when you check the logs or use “pgbackrest info” I see issues:
oc logs -f backrest-backup-op140tst-clu-d77qv
nss_wrapper: adding user
nss_wrapper: adding group
nss_wrapper: environment configured
Starting the pgBackRest repo
nss_wrapper: ssh configured
/usr/local/bin/pgbackrest-repo.sh: line 64: /etc/pgbackrest/pgbackrest.conf: Read-only file system
cp: cannot stat ‘/sshd/id_ed25519’: No such file or directory
chmod: cannot access ‘/tmp/id_ed25519’: No such file or directory
The pgBackRest repo has been started
/sshd/sshd_config: No such file or directory
oc exec -it op140tst-clu-backrest-shared-repo-674ffdd87-8pwwk – bash -c “pgbackrest info”
stanza: db
status: error (missing stanza path)
Looks like the stanza creation failed or didn’t happen at all. I cannot find any successful or failed “stanza” pgTask or job.
I tried to create the stanza manually myself using this yaml:
apiVersion: pg.percona.com/v1
kind: Pgtask
metadata:
labels:
pg-cluster: op140tst-clu
pgouser: admin
name: op140tst-clu-backrest-stanza-create
spec:
name: op140tst-clu-backrest-stanza-create
parameters:
backrest-command: stanza-create
backrest-opts: --log-level-stderr=debug
backrest-s3-verify-tls: “false”
backrest-storage-type: “s3”
job-name: op140tst-clu-backrest-stanza-create
pg-cluster: op140tst-clu
tasktype: backrest
The stanza creation also fails with:
oc logs -f op140tst-clu-backrest-stanza-create-vc6zb
nss_wrapper: adding user
nss_wrapper: adding group
nss_wrapper: environment configured
Starting the pgBackRest repo
nss_wrapper: ssh configured
/usr/local/bin/pgbackrest-repo.sh: line 64: /etc/pgbackrest/pgbackrest.conf: Read-only file system
cp: cannot stat ‘/sshd/id_ed25519’: No such file or directory
chmod: cannot access ‘/tmp/id_ed25519’: No such file or directory
The pgBackRest repo has been started
/sshd/sshd_config: No such file or directory
Does anyone have an idea what is different with operator 1.4.1 compared to 1.3.0?
What am I doing wrong here?
Thank you & best regards,
Martin