Log: /mnt/jenkins/workspace/cloud-psmdb-operator_PR-1976/e2e-tests/logs/replset-overrides.log WARNING: version difference between client (1.33) and server (1.30) exceeds the supported minor version skew of +/-1 WARNING: version difference between client (1.33) and server (1.30) exceeds the supported minor version skew of +/-1 WARNING: version difference between client (1.33) and server (1.30) exceeds the supported minor version skew of +/-1 ----------------------------------------------------------------------------------- get and delete old CRDs and RBAC ----------------------------------------------------------------------------------- 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-1976-c5e94123-1-cluster10" modified. ----------------------------------------------------------------------------------- start PSMDB operator ----------------------------------------------------------------------------------- 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-5ff9cd445c-shbk4 to be ready.OK Print operator info from log 2025-06-23T03:05:58.440Z INFO setup Manager starting up {"gitCommit": "c5e9412372539dd2795146fa7e07fb2a7cd41509", "gitBranch": "PR-1976-c5e94123", "buildTime": "", "goVersion": "go1.24.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 replset-overrides-12843 ----------------------------------------------------------------------------------- error: resource(s) were provided, but no name was specified ----------------------------------------------------------------------------------- create namespace replset-overrides-12843 ----------------------------------------------------------------------------------- namespace/replset-overrides-12843 created Context "gke_cloud-dev-112233_us-central1-a_jen-psmdb-1976-c5e94123-1-cluster10" modified. deployment.apps/psmdb-client created ----------------------------------------------------------------------------------- install Minio ----------------------------------------------------------------------------------- Error: uninstall: Release not loaded: minio-service: release: not found "minio" has been removed from your repositories "minio" has been added to your repositories NAME: minio-service LAST DEPLOYED: Mon Jun 23 03:06:15 2025 NAMESPACE: replset-overrides-12843 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.replset-overrides-12843.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace replset-overrides-12843 -l "release=minio-service" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace replset-overrides-12843 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 replset-overrides-12843 minio-service -o jsonpath="{.data.rootUser}" | base64 --decode):$(kubectl get secret --namespace replset-overrides-12843 minio-service -o jsonpath="{.data.rootPassword}" | base64 --decode)@localhost:9000 3. mc ls minio-service-local waiting for pod/minio-service-86dfccd949-frqrf to be ready.OK service/minio-service created make_bucket: operator-testing pod "aws-cli" deleted 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_replset-overrides-12843 ----------------------------------------------------------------------------------- Case 1: Deploying a new cluster with hostname overrides ----------------------------------------------------------------------------------- secret/some-users created secret/some-name-ssl created secret/some-name-ssl-internal created secret/minio-secret created creating external services service/external-rs0-0 created service/external-rs0-1 created service/external-rs0-2 created creating PSMDB cluster: some-name perconaservermongodb.psmdb.percona.com/some-name created 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. writing some data Percona Server for MongoDB shell version v4.4.29-28 connecting to: mongodb://external-rs0-0.replset-overrides-12843.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb&replicaSet=rs0&ssl=false Implicit session: session { "id" : UUID("99738641-fb73-477f-89e6-8e5e01c5809f") } Percona Server for MongoDB server version: v8.0.8-3 WARNING: shell and server versions do not match switched to db myApp WriteResult({ "nInserted" : 1 }) bye [2025-06-23T03:08:53+0000] running db.test.find() in myApp ----------------------------------------------------------------------------------- run backup backup-minio-physical ----------------------------------------------------------------------------------- perconaservermongodbbackup.psmdb.percona.com/backup-minio-physical created waiting for backup-minio-physical to reach ready state...... write data after backup Percona Server for MongoDB shell version v4.4.29-28 connecting to: mongodb://external-rs0-0.replset-overrides-12843.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb&replicaSet=rs0&ssl=false Implicit session: session { "id" : UUID("2087a9e2-8c9d-493b-bfa4-fadd213ff08c") } Percona Server for MongoDB server version: v8.0.8-3 WARNING: shell and server versions do not match switched to db myApp WriteResult({ "nInserted" : 1 }) bye restore to backup backup-minio-physical [2025-06-23T03:09:09+0000] running db.test.find() in myApp perconaservermongodbrestore.psmdb.percona.com/restore-backup-minio-physical created Waiting for the psmdb-restore/restore-backup-minio-physical object to be createdOK Waiting psmdb-restore/restore-backup-minio-physical to reach state "ready" ...OK after 3 minutes waiting for cluster readyness............... [2025-06-23T03:16:02+0000] running db.test.find() in myApp waiting for cluster readyness deleting cluster: some-name perconaservermongodb.psmdb.percona.com "some-name" deleted waiting for psmdb/some-name to be deletedError from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found Error from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found Error from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found Error from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found waiting for pod/some-name-rs0-0 to be deletedError from server (NotFound): pods "some-name-rs0-0" not found Error from server (NotFound): pods "some-name-rs0-0" not found Error from server (NotFound): pods "some-name-rs0-0" not found Error from server (NotFound): pods "some-name-rs0-0" not found secret "internal-some-name-users" deleted secret "minio-secret" deleted secret "minio-service" deleted secret "sh.helm.release.v1.minio-service.v1" deleted secret "some-name-mongodb-encryption-key" deleted secret "some-name-pbm-config" deleted secret "some-name-ssl" deleted secret "some-name-ssl-internal" deleted secret "some-users" deleted ----------------------------------------------------------------------------------- Case 1: PASSED ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- Case 2: Patching a running cluster to override hostnames ----------------------------------------------------------------------------------- secret/some-users created secret/some-name-ssl created secret/some-name-ssl-internal created secret/minio-secret created creating PSMDB cluster: some-name perconaservermongodb.psmdb.percona.com/some-name created 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.... writing some data Percona Server for MongoDB shell version v4.4.29-28 connecting to: mongodb://some-name-rs0-0.some-name-rs0.replset-overrides-12843.svc.cluster.local:27017,some-name-rs0-1.some-name-rs0.replset-overrides-12843.svc.cluster.local:27017,some-name-rs0-2.some-name-rs0.replset-overrides-12843.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb&replicaSet=rs0&ssl=false Implicit session: session { "id" : UUID("fce28d08-8dcd-4db6-9d4c-de6191adfd08") } Percona Server for MongoDB server version: v8.0.8-3 WARNING: shell and server versions do not match switched to db myApp WriteResult({ "nInserted" : 1 }) bye [2025-06-23T03:18:31+0000] running db.test.find() in myApp ----------------------------------------------------------------------------------- run backup backup-minio-logical ----------------------------------------------------------------------------------- perconaservermongodbbackup.psmdb.percona.com/backup-minio-logical created waiting for backup-minio-logical to reach ready state...... creating external services service/external-rs0-0 unchanged service/external-rs0-1 unchanged service/external-rs0-2 unchanged patching PSMDB cluster with replsetOverrides: some-name perconaservermongodb.psmdb.percona.com/some-name configured Waiting for cluster to reach ready state checking if we can read existing data [2025-06-23T03:18:50+0000] running db.test.find() in myApp write data after backup Percona Server for MongoDB shell version v4.4.29-28 connecting to: mongodb://external-rs0-0.replset-overrides-12843.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb&replicaSet=rs0&ssl=false Implicit session: session { "id" : UUID("416ec780-91a7-4629-96a3-07e331eaa651") } Percona Server for MongoDB server version: v8.0.8-3 WARNING: shell and server versions do not match switched to db myApp WriteResult({ "nInserted" : 1 }) bye restore to backup backup-minio-logical [2025-06-23T03:18:55+0000] running db.test.find() in myApp perconaservermongodbrestore.psmdb.percona.com/restore-backup-minio-logical created Waiting for the psmdb-restore/restore-backup-minio-logical object to be createdOK Waiting psmdb-restore/restore-backup-minio-logical to reach state "ready" OK after 0 minutes waiting for cluster readyness [2025-06-23T03:19:17+0000] running db.test.find() in myApp waiting for cluster readyness deleting cluster: some-name perconaservermongodb.psmdb.percona.com "some-name" deleted waiting for psmdb/some-name to be deletedError from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found Error from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found Error from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found Error from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found waiting for pod/some-name-rs0-0 to be deletedError from server (NotFound): pods "some-name-rs0-0" not found Error from server (NotFound): pods "some-name-rs0-0" not found Error from server (NotFound): pods "some-name-rs0-0" not found Error from server (NotFound): pods "some-name-rs0-0" not found secret "internal-some-name-users" deleted secret "minio-secret" deleted secret "some-name-mongodb-encryption-key" deleted secret "some-name-ssl" deleted secret "some-name-ssl-internal" deleted secret "some-users" deleted ----------------------------------------------------------------------------------- Case 2: PASSED ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- Case 3: Overriding member priorities ----------------------------------------------------------------------------------- secret/some-users created secret/some-name-ssl created secret/some-name-ssl-internal created secret/minio-secret created creating PSMDB cluster: some-name perconaservermongodb.psmdb.percona.com/some-name created 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..... writing some data Percona Server for MongoDB shell version v4.4.29-28 connecting to: mongodb://some-name-rs0-2.some-name-rs0.replset-overrides-12843.svc.cluster.local:27017,some-name-rs0-0.some-name-rs0.replset-overrides-12843.svc.cluster.local:27017,some-name-rs0-1.some-name-rs0.replset-overrides-12843.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb&replicaSet=rs0&ssl=false Implicit session: session { "id" : UUID("95c2057d-323b-4474-bc81-1fa51c5abb84") } Percona Server for MongoDB server version: v8.0.8-3 WARNING: shell and server versions do not match switched to db myApp WriteResult({ "nInserted" : 1 }) bye [2025-06-23T03:21:37+0000] running db.test.find() in myApp checking member priorities member priorities are OK deleting cluster: some-name perconaservermongodb.psmdb.percona.com "some-name" deleted waiting for psmdb/some-name to be deletedError from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found Error from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found Error from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found Error from server (NotFound): perconaservermongodbs.psmdb.percona.com "some-name" not found waiting for pod/some-name-rs0-0 to be deleted.Error from server (NotFound): pods "some-name-rs0-0" not found Error from server (NotFound): pods "some-name-rs0-0" not found Error from server (NotFound): pods "some-name-rs0-0" not found Error from server (NotFound): pods "some-name-rs0-0" not found secret "internal-some-name-users" deleted secret "minio-secret" deleted secret "some-name-mongodb-encryption-key" deleted secret "some-name-ssl" deleted secret "some-name-ssl-internal" deleted secret "some-users" deleted ----------------------------------------------------------------------------------- Case 3: PASSED ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- All cases PASSED -----------------------------------------------------------------------------------