Log: /mnt/jenkins/workspace/cloud-psmdb-operator_PR-2269/e2e-tests/logs/balancer.log Warning: version difference between client (1.36) and server (1.32) exceeds the supported minor version skew of +/-1 Warning: version difference between client (1.36) and server (1.32) exceeds the supported minor version skew of +/-1 Warning: version difference between client (1.36) 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-20e73be3-5-cluster2" modified. ----------------------------------------------------------------------------------- start PSMDB operator: docker.io/perconalab/percona-server-mongodb-operator:PR-2269-20e73be3 ----------------------------------------------------------------------------------- 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-dfddcf789-mgmtn to be ready.OK Print operator info from log 2026-04-23T08:23:10.501Z INFO setup Manager starting up {"gitCommit": "20e73be336bc9107fc60a16452f9669066123774", "gitBranch": "PR-2269-20e73be3", "buildTime": "", "goVersion": "go1.25.9", "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 balancer-2395 ----------------------------------------------------------------------------------- error: resource(s) were provided, but no name was specified ----------------------------------------------------------------------------------- create namespace balancer-2395 ----------------------------------------------------------------------------------- namespace/balancer-2395 created Context "gke_cloud-dev-112233_us-central1-a_jen-psmdb-2269-20e73be3-5-cluster2" modified. ----------------------------------------------------------------------------------- install MinIO: minio-service ----------------------------------------------------------------------------------- "minio" has been added to your repositories NAME: minio-service LAST DEPLOYED: Thu Apr 23 08:23:46 2026 NAMESPACE: balancer-2395 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.balancer-2395.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace balancer-2395 -l "release=minio-service" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace balancer-2395 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 balancer-2395 minio-service -o jsonpath="{.data.rootUser}" | base64 --decode):$(kubectl get secret --namespace balancer-2395 minio-service -o jsonpath="{.data.rootPassword}" | base64 --decode)@localhost:9000 3. mc ls minio-service-local waiting for pod/minio-service-6d5f646cdc-qthgz to be ready.OK service/minio-service created make_bucket: operator-testing pod "aws-cli" deleted from balancer-2395 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. ----------------------------------------------------------------------------------- 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 [2026-04-23T08:24:31+0000] create PSMDB cluster secret/some-users created deployment.apps/psmdb-client created perconaservermongodb.psmdb.percona.com/some-name created [2026-04-23T08:24:36+0000] check if cfg pods started 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 [2026-04-23T08:26:22+0000] check if all shards 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 pod/some-name-rs1-0 to be ready.OK waiting for pod/some-name-rs1-1 to be ready.OK waiting for pod/some-name-rs1-2 to be ready.OK waiting for pod/some-name-rs2-0 to be ready.OK waiting for pod/some-name-rs2-1 to be ready.OK waiting for pod/some-name-rs2-2 to be ready.OK [2026-04-23T08:27:12+0000] check if mongos pods started 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........... [2026-04-23T08:28:30+0000] sleeping for 10 seconds... checking if balancer status is true...OK [2026-04-23T08:28:44+0000] create user [direct: mongos] admin> { ok: 1, '$clusterTime': { clusterTime: Timestamp({ t: 1776932927, i: 7 }), signature: { hash: Binary.createFromBase64('slJAgKgy5ryRmyEq6QdmtxYGw9w=', 0), keyId: Long('7631868125750755351') } }, operationTime: Timestamp({ t: 1776932927, i: 7 }) } [direct: mongos] admin> [2026-04-23T08:28:50+0000] enable sharding [direct: mongos] admin> { ok: 1, '$clusterTime': { clusterTime: Timestamp({ t: 1776932933, i: 11 }), signature: { hash: Binary.createFromBase64('BYYGG+illHhWoka/0MA04cEIp9o=', 0), keyId: Long('7631868125750755351') } }, operationTime: Timestamp({ t: 1776932933, i: 8 }) } [direct: mongos] admin> [2026-04-23T08:28:55+0000] shard collection [direct: mongos] admin> { collectionsharded: 'app.city', ok: 1, '$clusterTime': { clusterTime: Timestamp({ t: 1776932939, i: 37 }), signature: { hash: Binary.createFromBase64('DtKEXwJLhUhlw/3eioapvm/MwnM=', 0), keyId: Long('7631868125750755351') } }, operationTime: Timestamp({ t: 1776932939, i: 36 }) } [direct: mongos] admin> [2026-04-23T08:28:59+0000] write data (this can take some time, be patient) [2026-04-23T08:30:50+0000] running backup: backup-minio-0 [2026-04-23T08:30:50+0000] running backup backup-minio-0 perconaservermongodbbackup.psmdb.percona.com/backup-minio-0 created waiting for backup-minio-0 to reach requested state..OK [2026-04-23T08:30:54+0000] checking if balancer is disabled [2026-04-23T08:30:54+0000] sleeping for 0 seconds... checking if balancer status is false...OK waiting for backup-minio-0 to reach ready state...............OK [2026-04-23T08:31:27+0000] checking if balancer is true after backup [2026-04-23T08:31:27+0000] sleeping for 10 seconds... checking if balancer status is true...OK [2026-04-23T08:31:40+0000] running restore: restore-backup-minio-0 [2026-04-23T08:31:40+0000] running restore restore-backup-minio-0 perconaservermongodbrestore.psmdb.percona.com/restore-backup-minio-0 created Waiting for the psmdb-restore/restore-backup-minio-0 object to be created.OK Waiting psmdb-restore/restore-backup-minio-0 to reach state "requested" .OK after 0 minutes [2026-04-23T08:32:04+0000] checking if balancer is disabled [2026-04-23T08:32:04+0000] sleeping for 0 seconds... checking if balancer status is false...OK Waiting for the psmdb-restore/restore-backup-minio-0 object to be created.OK Waiting psmdb-restore/restore-backup-minio-0 to reach state "ready" .2026-04-23T08:32:45.413Z DEBUG checking if restore is allowed {"controller": "psmdbrestore-controller", "controllerGroup": "psmdb.percona.com", "controllerKind": "PerconaServerMongoDBRestore", "PerconaServerMongoDBRestore": {"name":"restore-backup-minio-0","namespace":"balancer-2395"}, "namespace": "balancer-2395", "name": "restore-backup-minio-0", "reconcileID": "8a871468-3cdb-4471-900d-c2de28024ba7", "cluster": "some-name", "namespace": "balancer-2395"} 2026-04-23T08:32:45.708Z INFO Restore state changed {"controller": "psmdbrestore-controller", "controllerGroup": "psmdb.percona.com", "controllerKind": "PerconaServerMongoDBRestore", "PerconaServerMongoDBRestore": {"name":"restore-backup-minio-0","namespace":"balancer-2395"}, "namespace": "balancer-2395", "name": "restore-backup-minio-0", "reconcileID": "8a871468-3cdb-4471-900d-c2de28024ba7", "previous": "requested", "current": "error"} apiVersion: psmdb.percona.com/v1 kind: PerconaServerMongoDBRestore metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"psmdb.percona.com/v1","kind":"PerconaServerMongoDBRestore","metadata":{"annotations":{},"name":"restore-backup-minio-0","namespace":"balancer-2395"},"spec":{"backupName":"backup-minio-0","clusterName":"some-name"}} creationTimestamp: "2026-04-23T08:31:43Z" generation: 1 name: restore-backup-minio-0 namespace: balancer-2395 resourceVersion: "1776933165735519006" uid: 716b5520-41ed-4187-9e9d-f7ed900c74f0 spec: backupName: backup-minio-0 clusterName: some-name status: error: 'mongorestore: restore mongo dump (successes: 5 / fails: 0): corruption found in archive; I/O error reading length or terminator ( compose: write namespaces: new reader: download: "admin.pbmRRoles.gz": get file stat: get S3 object header: operation error S3: HeadObject, https response error StatusCode: 499, RequestID: 18A8EF445E6542DD, HostID: dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8, api error UnknownError: UnknownError )' pbmName: "2026-04-23T08:32:04.204145632Z" state: error Name: restore-backup-minio-0 Namespace: balancer-2395 Labels: Annotations: API Version: psmdb.percona.com/v1 Kind: PerconaServerMongoDBRestore Metadata: Creation Timestamp: 2026-04-23T08:31:43Z Generation: 1 Resource Version: 1776933165735519006 UID: 716b5520-41ed-4187-9e9d-f7ed900c74f0 Spec: Backup Name: backup-minio-0 Cluster Name: some-name Status: Error: mongorestore: restore mongo dump (successes: 5 / fails: 0): corruption found in archive; I/O error reading length or terminator ( compose: write namespaces: new reader: download: "admin.pbmRRoles.gz": get file stat: get S3 object header: operation error S3: HeadObject, https response error StatusCode: 499, RequestID: 18A8EF445E6542DD, HostID: dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8, api error UnknownError: UnknownError ) Pbm Name: 2026-04-23T08:32:04.204145632Z State: error Events: Restore object restore-backup-minio-0 is in error state after 1 minutes. something went wrong with operator or kubernetes cluster