Getting error "Waiting for restore metadata" while restoring mongodb

Description:

I am testing restoration from s3 compatible r2 bucket (cloudflare) full backup restoration.

Version:

percona/percona-server-mongodb-operator:1.16.2
percona/percona-server-mongodb:6.0.16-13

Logs:

these are mongodb percona operator logs:

2025-07-10T10:22:49.367Z INFO Waiting for restore metadata {controller: psmdbrestore-controller, object: {name:restore23,namespace:test-mongodb}, namespace: test-mongodb, name: restore23, reconcileID: c1b574e9-29ed-44b0-bd73-d3aae28493ea, pbmName: 2025-07-10T10:17:25.306065442Z, restore: restore23, backup: }
2025-07-10T10:22:54.446Z INFO Waiting for restore metadata {controller: psmdbrestore-controller, object: {name:restore23,namespace:test-mongodb}, namespace: test-mongodb, name: restore23, reconcileID: c62ce922-a4e8-4803-8f3e-937de783c444, pbmName: 2025-07-10T10:17:25.306065442Z, restore: restore23, backup: }

Additional Information:

My restore yaml which i am using is:

apiVersion: psmdb.percona.com/v1
kind: PerconaServerMongoDBRestore
metadata:
  name: restore1234
spec:
  clusterName: mongo-db
  backupSource:
    type: physical
    destination: s3://devops/integration/mongodb/2025-07-07T16:00:21Z/
    s3:
      credentialsSecret: mongodb-mongo-db-secrets-c8b7f20e
      region: us-east-1
      bucket: devops
      endpointUrl: https://4b92451476ed49bcf987231b504ca149.r2.cloudflarestorage.com
      prefix: /integration/mongodb/
  pitr:
    type: date
    date: 2025-07-07 16:00:21

I need to know whats the correct yaml file to complete my restoration process.

Percona team, please take a look and let me know if I’m doing anything incorrectly.

Please percona team help me in this.

Hi, your yaml file looks correct. Have you checked logs at the container/pod level? Example:

$ kubectl logs <operator-pod>
$ kubectl logs <cluster>-rs0-0 pbm-agent # repeat for each rs0 pod

If you suspect a bug I suggest opening a ticket Jira - Percona JIRA

The log I’m receiving from the operator indicates “Waiting for restore metadata,” which I’ve already mentioned above.
I don’t have any other logs available because during the restoration process, only the operator pod is active while the others are in a terminated state.