Log: /mnt/jenkins/workspace/cloud-psmdb-operator_PR-2269/e2e-tests/logs/demand-backup-physical-sharded-parallel.log Warning: version difference between client (1.35) and server (1.32) exceeds the supported minor version skew of +/-1 Warning: version difference between client (1.35) and server (1.32) exceeds the supported minor version skew of +/-1 Warning: version difference between client (1.35) and server (1.32) exceeds the supported minor version skew of +/-1 ----------------------------------------------------------------------------------- get and delete old CRDs and RBAC ----------------------------------------------------------------------------------- grep: warning: stray \ before - grep: warning: stray \ before - error: the server doesn't have a resource type "perconaservermongodbbackups" + kubectl patch perconaservermongodbbackups.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}' error: the server doesn't have a resource type "perconaservermongodbbackups" error: the server doesn't have a resource type "perconaservermongodbrestores" + kubectl patch perconaservermongodbrestores.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}' error: the server doesn't have a resource type "perconaservermongodbrestores" error: the server doesn't have a resource type "perconaservermongodbs" + kubectl patch perconaservermongodbs.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}' error: the server doesn't have a resource type "perconaservermongodbs" Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "null" not found Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "null" not found Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "null" not found Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "null" not found ----------------------------------------------------------------------------------- destroy chaos-mesh ----------------------------------------------------------------------------------- error: resource(s) were provided, but no name was specified error: resource(s) were provided, but no name was specified error: resource(s) were provided, but no name was specified error: resource(s) were provided, but no name was specified error: resource(s) were provided, but no name was specified error: resource(s) were provided, but no name was specified ----------------------------------------------------------------------------------- cleaned up all old namespaces ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- cleaned up old namespaces psmdb-operator ----------------------------------------------------------------------------------- error: resource(s) were provided, but no name was specified ----------------------------------------------------------------------------------- create namespace psmdb-operator ----------------------------------------------------------------------------------- namespace/psmdb-operator created Context "gke_cloud-dev-112233_us-central1-a_jen-psmdb-2269-c00cf2f2-4-cluster3" modified. ----------------------------------------------------------------------------------- start PSMDB operator: docker.io/perconalab/percona-server-mongodb-operator:PR-2269-c00cf2f2 ----------------------------------------------------------------------------------- customresourcedefinition.apiextensions.k8s.io/perconaservermongodbbackups.psmdb.percona.com serverside-applied customresourcedefinition.apiextensions.k8s.io/perconaservermongodbrestores.psmdb.percona.com serverside-applied customresourcedefinition.apiextensions.k8s.io/perconaservermongodbs.psmdb.percona.com serverside-applied clusterrole.rbac.authorization.k8s.io/percona-server-mongodb-operator created serviceaccount/percona-server-mongodb-operator created clusterrolebinding.rbac.authorization.k8s.io/service-account-percona-server-mongodb-operator created deployment.apps/percona-server-mongodb-operator created waiting for pod/percona-server-mongodb-operator-f4cfd7898-7fmtm to be ready.OK Print operator info from log 2026-03-26T11:50:59.041Z INFO setup Manager starting up {"gitCommit": "c00cf2f277367cd89c8ffccbcdfeb3ff7ec457a4", "gitBranch": "PR-2269-c00cf2f2", "buildTime": "", "goVersion": "go1.25.8", "os": "linux", "arch": "amd64"} ----------------------------------------------------------------------------------- destroy chaos-mesh ----------------------------------------------------------------------------------- error: resource(s) were provided, but no name was specified error: resource(s) were provided, but no name was specified error: resource(s) were provided, but no name was specified error: resource(s) were provided, but no name was specified error: resource(s) were provided, but no name was specified error: resource(s) were provided, but no name was specified ----------------------------------------------------------------------------------- cleaned up all old namespaces ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- cleaned up old namespaces demand-backup-physical-sharded-parallel-5166 ----------------------------------------------------------------------------------- error: resource(s) were provided, but no name was specified ----------------------------------------------------------------------------------- create namespace demand-backup-physical-sharded-parallel-5166 ----------------------------------------------------------------------------------- namespace/demand-backup-physical-sharded-parallel-5166 created Context "gke_cloud-dev-112233_us-central1-a_jen-psmdb-2269-c00cf2f2-4-cluster3" modified. ----------------------------------------------------------------------------------- install MinIO: minio-service ----------------------------------------------------------------------------------- "minio" has been removed from your repositories "minio" has been added to your repositories NAME: minio-service LAST DEPLOYED: Thu Mar 26 11:51:29 2026 NAMESPACE: demand-backup-physical-sharded-parallel-5166 STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: MinIO can be accessed via port 9000 on the following DNS name from within your cluster: minio-service.demand-backup-physical-sharded-parallel-5166.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace demand-backup-physical-sharded-parallel-5166 -l "release=minio-service" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace demand-backup-physical-sharded-parallel-5166 Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect to MinIO server with mc client: 1. Download the MinIO mc client - https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart 2. export MC_HOST_minio-service-local=http://$(kubectl get secret --namespace demand-backup-physical-sharded-parallel-5166 minio-service -o jsonpath="{.data.rootUser}" | base64 --decode):$(kubectl get secret --namespace demand-backup-physical-sharded-parallel-5166 minio-service -o jsonpath="{.data.rootPassword}" | base64 --decode)@localhost:9000 3. mc ls minio-service-local waiting for pod/minio-service-6d5f646cdc-9zjpd to be ready.OK service/minio-service created make_bucket: operator-testing pod "aws-cli" deleted from demand-backup-physical-sharded-parallel-5166 namespace All commands and output from this session will be recorded in container logs, including credentials and sensitive information passed through the command prompt. If you don't see a command prompt, try pressing enter. warning: couldn't attach to pod/aws-cli, falling back to streaming logs: Internal error occurred: unable to upgrade connection: container aws-cli not found in pod aws-cli_demand-backup-physical-sharded-parallel-5166 ----------------------------------------------------------------------------------- create secrets for cloud storages ----------------------------------------------------------------------------------- secret/minio-secret created secret/aws-s3-secret created secret/gcp-cs-secret created secret/azure-secret created secret/gcp-cs-sa-key-secret created ----------------------------------------------------------------------------------- Testing on sharded cluster ----------------------------------------------------------------------------------- Creating PSMDB cluster secret/some-users created perconaservermongodb.psmdb.percona.com/some-name created deployment.apps/psmdb-client created check if all pods started waiting for pod/some-name-rs0-0 to be ready......OK waiting for pod/some-name-rs0-1 to be ready.......OK waiting for pod/some-name-rs0-2 to be ready.........OK Waiting for cluster readyness......................................................... waiting for pod/some-name-cfg-0 to be ready.OK waiting for pod/some-name-cfg-1 to be ready.OK waiting for pod/some-name-cfg-2 to be ready.OK Waiting for cluster readyness waiting for pod/some-name-mongos-0 to be ready.OK waiting for pod/some-name-mongos-1 to be ready.OK waiting for pod/some-name-mongos-2 to be ready.OK Waiting for cluster readyness waiting for cluster readyness.OK Percona Server for MongoDB shell version v4.4.29-28 connecting to: mongodb://some-name-mongos.demand-backup-physical-sharded-parallel-5166.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb Implicit session: session { "id" : UUID("2309e3e3-5d6b-4a69-ba34-5d0518212daf") } Percona Server for MongoDB server version: v8.0.19-7 WARNING: shell and server versions do not match Successfully added user: { "user" : "myApp", "roles" : [ { "db" : "myApp", "role" : "readWrite" } ] } bye Percona Server for MongoDB shell version v4.4.29-28 connecting to: mongodb://some-name-mongos.demand-backup-physical-sharded-parallel-5166.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb Implicit session: session { "id" : UUID("b2bb3eeb-b941-44b9-9543-d637eb9d0b4e") } Percona Server for MongoDB server version: v8.0.19-7 WARNING: shell and server versions do not match switched to db myApp WriteResult({ "nInserted" : 1 }) bye [2026-03-26T11:56:07+0000] running db.test.command() in myApp Waiting 60 seconds for stable timestamp in wiredtiger Running backups [2026-03-26T11:57:29+0000] running backup backup-minio-sharded perconaservermongodbbackup.psmdb.percona.com/backup-minio-sharded created [2026-03-26T11:57:32+0000] running backup backup-aws-s3-sharded perconaservermongodbbackup.psmdb.percona.com/backup-aws-s3-sharded created [2026-03-26T11:57:34+0000] running backup backup-gcp-cs-sharded perconaservermongodbbackup.psmdb.percona.com/backup-gcp-cs-sharded created [2026-03-26T11:57:35+0000] running backup backup-azure-blob-sharded perconaservermongodbbackup.psmdb.percona.com/backup-azure-blob-sharded created waiting for backup-aws-s3-sharded to reach ready state................................OK AWS credentials already set in environment Backup operator-testing/psmdb-demand-backup-physical-sharded/2026-03-26T11:57:50Z//rs0/filelist.pbm found in aws-s3 AWS credentials already set in environment Backup operator-testing/psmdb-demand-backup-physical-sharded/2026-03-26T11:57:50Z//cfg/filelist.pbm found in aws-s3 waiting for backup-gcp-cs-sharded to reach ready state..................OK Setting up GCS credentials from K8s secret: gcp-cs-secret GCS credentials configured successfully Backup gs://operator-testing/psmdb-demand-backup-physical-sharded/2026-03-26T11:58:32Z/rs0/filelist.pbm found in gcp-cs Setting up GCS credentials from K8s secret: gcp-cs-secret GCS credentials configured successfully Backup gs://operator-testing/psmdb-demand-backup-physical-sharded/2026-03-26T11:58:32Z/cfg/filelist.pbm found in gcp-cs waiting for backup-azure-blob-sharded to reach ready state................OK Setting up Azure credentials from K8s secret: azure-secret Azure credentials configured successfully Backup psmdb-demand-backup-physical-sharded/2026-03-26T11:59:11Z/rs0/filelist.pbm found in azure-blob Setting up Azure credentials from K8s secret: azure-secret Azure credentials configured successfully Backup psmdb-demand-backup-physical-sharded/2026-03-26T11:59:11Z/cfg/filelist.pbm found in azure-blob waiting for backup-minio-sharded to reach ready state..OK 2026-03-26 11:57:45 11018 filelist.pbm Drop collection Percona Server for MongoDB shell version v4.4.29-28 connecting to: mongodb://some-name-mongos.demand-backup-physical-sharded-parallel-5166.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb Implicit session: session { "id" : UUID("879578b6-0a17-4148-8d65-1538650e7197") } Percona Server for MongoDB server version: v8.0.19-7 WARNING: shell and server versions do not match switched to db myApp true bye ----------------------------------------------------------------------------------- destroy cluster/operator and all other resources ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- Delete psmdb-backup ----------------------------------------------------------------------------------- NAME CLUSTER STORAGE DESTINATION TYPE SIZE STATUS COMPLETED AGE backup-aws-s3-sharded some-name aws-s3 s3://operator-testing/psmdb-demand-backup-physical-sharded/2026-03-26T11:57:50Z physical 2.83MB ready 96s 2m34s backup-azure-blob-sharded some-name azure-blob azure://operator-testing/psmdb-demand-backup-physical-sharded/2026-03-26T11:59:11Z physical 4.10MB ready 20s 2m30s backup-gcp-cs-sharded some-name gcp-cs s3://operator-testing/psmdb-demand-backup-physical-sharded/2026-03-26T11:58:32Z physical 3.09MB ready 60s 2m32s backup-minio-sharded some-name minio s3://operator-testing/2026-03-26T11:57:32Z physical 1.98MB ready 2m22s 2m36s perconaservermongodbbackup.psmdb.percona.com "backup-aws-s3-sharded" deleted from demand-backup-physical-sharded-parallel-5166 namespace perconaservermongodbbackup.psmdb.percona.com "backup-azure-blob-sharded" deleted from demand-backup-physical-sharded-parallel-5166 namespace perconaservermongodbbackup.psmdb.percona.com "backup-gcp-cs-sharded" deleted from demand-backup-physical-sharded-parallel-5166 namespace perconaservermongodbbackup.psmdb.percona.com "backup-minio-sharded" deleted from demand-backup-physical-sharded-parallel-5166 namespace ----------------------------------------------------------------------------------- get and delete old CRDs and RBAC ----------------------------------------------------------------------------------- customresourcedefinition.apiextensions.k8s.io "perconaservermongodbbackups.psmdb.percona.com" deleted customresourcedefinition.apiextensions.k8s.io "perconaservermongodbrestores.psmdb.percona.com" deleted customresourcedefinition.apiextensions.k8s.io "perconaservermongodbs.psmdb.percona.com" deleted grep: warning: stray \ before - grep: warning: stray \ before - error: the server doesn't have a resource type "perconaservermongodbbackups" + kubectl patch perconaservermongodbbackups.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}' error: the server doesn't have a resource type "perconaservermongodbbackups" error: the server doesn't have a resource type "perconaservermongodbrestores" + kubectl patch perconaservermongodbrestores.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}' error: the server doesn't have a resource type "perconaservermongodbrestores" error: the server doesn't have a resource type "perconaservermongodbs" + kubectl patch perconaservermongodbs.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}' error: the server doesn't have a resource type "perconaservermongodbs" clusterrole.rbac.authorization.k8s.io "percona-server-mongodb-operator" deleted clusterrolebinding.rbac.authorization.k8s.io "service-account-percona-server-mongodb-operator" deleted Terminated