Log: /mnt/jenkins/workspace/cloud-psmdb-operator_PR-2409/e2e-tests/logs/pitr-physical.log Warning: version difference between client (1.36) and server (1.33) exceeds the supported minor version skew of +/-1 Warning: version difference between client (1.36) and server (1.33) exceeds the supported minor version skew of +/-1 Warning: version difference between client (1.36) and server (1.33) 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 "perconaservermongodbclustersyncs" + kubectl patch perconaservermongodbclustersyncs.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}' error: the server doesn't have a resource type "perconaservermongodbclustersyncs" 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-2409-631b79c7b-9-cluster9" modified. ----------------------------------------------------------------------------------- start PSMDB operator: docker.io/perconalab/percona-server-mongodb-operator:PR-2409-631b79c7b ----------------------------------------------------------------------------------- customresourcedefinition.apiextensions.k8s.io/perconaservermongodbbackups.psmdb.percona.com serverside-applied customresourcedefinition.apiextensions.k8s.io/perconaservermongodbclustersyncs.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-66ccb7fd4-rc8zt to be ready.OK Print operator info from log 2026-06-22T16:20:46.284Z INFO setup Manager starting up {"gitCommit": "631b79c7bad9f6f83d39b94b8f96a438036de06a", "gitBranch": "PR-2409-631b79c7b", "buildTime": "", "goVersion": "go1.26.4", "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 pitr-physical-22223 ----------------------------------------------------------------------------------- error: resource(s) were provided, but no name was specified ----------------------------------------------------------------------------------- create namespace pitr-physical-22223 ----------------------------------------------------------------------------------- namespace/pitr-physical-22223 created Context "gke_cloud-dev-112233_us-central1-a_jen-psmdb-2409-631b79c7b-9-cluster9" modified. ----------------------------------------------------------------------------------- install MinIO: minio-service ----------------------------------------------------------------------------------- "minio" has been removed from your repositories "minio" has been added to your repositories NAME: minio-service LAST DEPLOYED: Mon Jun 22 16:21:23 2026 NAMESPACE: pitr-physical-22223 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.pitr-physical-22223.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace pitr-physical-22223 -l "release=minio-service" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace pitr-physical-22223 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 pitr-physical-22223 minio-service -o jsonpath="{.data.rootUser}" | base64 --decode):$(kubectl get secret --namespace pitr-physical-22223 minio-service -o jsonpath="{.data.rootPassword}" | base64 --decode)@localhost:9000 3. mc ls minio-service-local waiting for pod/minio-service-6d5f646cdc-jdrnv to be ready.OK service/minio-service created make_bucket: operator-testing make_bucket: operator-testing pod "aws-cli" deleted from pitr-physical-22223 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_pitr-physical-22223 ----------------------------------------------------------------------------------- create secrets and start client ----------------------------------------------------------------------------------- secret/some-users created deployment.apps/psmdb-client created secret/minio-secret created ----------------------------------------------------------------------------------- create first PSMDB cluster some-name ----------------------------------------------------------------------------------- perconaservermongodb.psmdb.percona.com/some-name created ----------------------------------------------------------------------------------- check if all 3 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 ----------------------------------------------------------------------------------- write data ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- create user myApp ----------------------------------------------------------------------------------- Percona Server for MongoDB shell version v4.4.29-28 connecting to: mongodb://some-name-mongos.pitr-physical-22223.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb Implicit session: session { "id" : UUID("7fbd8cee-5d5d-463e-b6ff-9aa344fcbf52") } Percona Server for MongoDB server version: v8.0.23-10 WARNING: shell and server versions do not match Successfully added user: { "user" : "myApp", "roles" : [ { "db" : "myApp", "role" : "readWrite" } ] } bye [2026-06-22T16:25:49+0000] write initial data, read from all Percona Server for MongoDB shell version v4.4.29-28 connecting to: mongodb://some-name-mongos.pitr-physical-22223.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb Implicit session: session { "id" : UUID("6886ec53-0d52-4e8a-9fb9-16faf94fd986") } Percona Server for MongoDB server version: v8.0.23-10 WARNING: shell and server versions do not match switched to db myApp WriteResult({ "nInserted" : 1 }) bye [2026-06-22T16:25:52+0000] running db.test.command() in myApp ----------------------------------------------------------------------------------- wait for pbm agents to start ----------------------------------------------------------------------------------- waiting for pbm-agent to be ready in some-name-rs0-0...2026-06-22T16:25:09.000+0000 I listening for the commands waiting for pbm-agent to be ready in some-name-rs0-1...2026-06-22T16:25:15.000+0000 I listening for the commands waiting for pbm-agent to be ready in some-name-rs0-2...2026-06-22T16:25:18.000+0000 I listening for the commands waiting for pbm-agent to be ready in some-name-rs1-0...2026-06-22T16:25:11.000+0000 I listening for the commands waiting for pbm-agent to be ready in some-name-rs1-1...2026-06-22T16:25:15.000+0000 I listening for the commands waiting for pbm-agent to be ready in some-name-rs1-2...2026-06-22T16:25:18.000+0000 I listening for the commands waiting for pbm-agent to be ready in some-name-rs2-0...2026-06-22T16:25:11.000+0000 I listening for the commands waiting for pbm-agent to be ready in some-name-rs2-1...2026-06-22T16:25:16.000+0000 I listening for the commands waiting for pbm-agent to be ready in some-name-rs2-2...2026-06-22T16:25:19.000+0000 I listening for the commands [2026-06-22T16:26:07+0000] Sleeping for 360 seconds to avoid PBM-1265 ----------------------------------------------------------------------------------- run backup backup-minio-2 ----------------------------------------------------------------------------------- perconaservermongodbbackup.psmdb.percona.com/backup-minio-2 created waiting for backup-minio-2 to reach ready state..........OK [2026-06-22T16:32:35+0000] write initial data, read from all error: Internal error occurred: error sending request: Post "https://10.216.0.54:10250/exec/pitr-physical-22223/psmdb-client-bb8b97679-bjmpk/psmdb-client?command=bash&command=-c&command=printf+%27use+myApp%5Cn+db.test.insert%28%7B+x%3A+100500+%7D%29%5Cn%27+%7C+mongo+mongodb%3A%2F%2FmyApp%3AmyPass%40some-name-mongos.pitr-physical-22223.svc.cluster.local%3A27017%2Fadmin+&error=1&output=1": dial timeout, backstop error: Internal error occurred: error sending request: Post "https://10.216.0.54:10250/exec/pitr-physical-22223/psmdb-client-bb8b97679-bjmpk/psmdb-client?command=bash&command=-c&command=printf+%27use+myApp%5Cn+db.test.insert%28%7B+x%3A+100500+%7D%29%5Cn%27+%7C+mongo+mongodb%3A%2F%2FmyApp%3AmyPass%40some-name-mongos.pitr-physical-22223.svc.cluster.local%3A27017%2Fadmin+&error=1&output=1": No agent available error: Internal error occurred: error sending request: Post "https://10.216.0.54:10250/exec/pitr-physical-22223/psmdb-client-bb8b97679-bjmpk/psmdb-client?command=bash&command=-c&command=printf+%27use+myApp%5Cn+db.test.insert%28%7B+x%3A+100500+%7D%29%5Cn%27+%7C+mongo+mongodb%3A%2F%2FmyApp%3AmyPass%40some-name-mongos.pitr-physical-22223.svc.cluster.local%3A27017%2Fadmin+&error=1&output=1": No agent available error: Internal error occurred: error sending request: Post "https://10.216.0.54:10250/exec/pitr-physical-22223/psmdb-client-bb8b97679-bjmpk/psmdb-client?command=bash&command=-c&command=printf+%27use+myApp%5Cn+db.test.insert%28%7B+x%3A+100500+%7D%29%5Cn%27+%7C+mongo+mongodb%3A%2F%2FmyApp%3AmyPass%40some-name-mongos.pitr-physical-22223.svc.cluster.local%3A27017%2Fadmin+&error=1&output=1": No agent available