I’m using the helm chart psmdb-operator and psmdb-db under percona-helm-charts/charts at main · percona/percona-helm-charts · GitHub to deploy a sharded MongoDB.
It was version 1.11.0 and now upgraded to 1.12.0, however, I can’t trigger a successful backup for both of them.
The backup image located on AWS ECR for pulling.
The secret mongodb-backup-s3 is configured with AWS access id&key, the CRD is upgraded using percona-server-mongodb-operator/crd.yaml at v1.12.0 · percona/percona-server-mongodb-operator · GitHub.
And the backup section configuration like this:
backup: enabled: true image: repository: xxxxx.dkr.ecr.cn-northwest-1.amazonaws.com.cn/percona/percona-backup-mongodb tag: 1.8.1 serviceAccountName: xxxx-mongodb-operator-psmdb-operator resources: limits: cpu: "300m" memory: "1G" requests: cpu: "100m" memory: "128Mi" storages: s3-cn-northwest: type: s3 s3: bucket: mongodb-backup credentialsSecret: mongodb-backup-s3 # endpointUrl: s3.cn-northwest-1.amazonaws.com.cn region: cn-northwest-1 prefix: "" pitr: enabled: false # oplogSpanMin: 10 tasks: - name: daily-s3 enabled: true schedule: "0 0 * * *" keep: 30 storageName: s3-cn-northwest compressionType: gzip
The operator successfully proceed to create the cronjob and trigger the psmdb-backup accordingly, but there is no verbose event except for:
$ kubectl describe psmdb-backup xxx Spec: Cluster Name: xxx-mongodb-psmdb-db Compression Type: gzip Storage Name: s3-cn-northwest Status: Azure: Credentials Secret: Destination: 2022-09-08T02:58:59Z Error: starting deadline exceeded Last Transition: 2022-09-08T02:58:59Z Pbm Name: 2022-09-08T02:58:59Z s3: Bucket: mongodb-backup Credentials Secret: mongodb-backup-s3 Endpoint URL: https://s3.cn-northwest-1.amazonaws.com.cn Region: cn-northwest-1 Start: 2022-09-08T02:58:59Z State: error Storage Name: s3-cn-northwest Events: <none>
The only hint I can see is the Error: starting deadline exceeded, what does this mean? I tried to configure the storage.s3.endpointUrl to AWS China specifically yet failed.
Is there anything I can leverage to troubleshoot?