Log: /mnt/jenkins/workspace/cloud-pxc-operator_PR-2473/e2e-tests/logs/demand-backup-flow-control-8-4.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 No resources found + kubectl patch pxc -n sh --type=merge -p '{"metadata":{"finalizers":[]}}' error: resource(s) were provided, but no name was specified No resources found No resources found No resources found 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 pxc-operator ----------------------------------------------------------------------------------- error: resource(s) were provided, but no name was specified namespace "pxc-operator" deleted waiting for namespace/pxc-operator to be deletedError from server (NotFound): namespaces "pxc-operator" not found ----------------------------------------------------------------------------------- create namespace pxc-operator ----------------------------------------------------------------------------------- namespace/pxc-operator created Context "gke_cloud-dev-112233_us-central1-a_jen-pxc-2473-6d392bea-4-cluster6" modified. ----------------------------------------------------------------------------------- start PXC operator ----------------------------------------------------------------------------------- customresourcedefinition.apiextensions.k8s.io/perconaxtradbclusterbackups.pxc.percona.com serverside-applied customresourcedefinition.apiextensions.k8s.io/perconaxtradbclusterrestores.pxc.percona.com serverside-applied customresourcedefinition.apiextensions.k8s.io/perconaxtradbclusters.pxc.percona.com serverside-applied clusterrole.rbac.authorization.k8s.io/percona-xtradb-cluster-operator unchanged serviceaccount/percona-xtradb-cluster-operator created clusterrolebinding.rbac.authorization.k8s.io/service-account-percona-xtradb-cluster-operator unchanged deployment.apps/percona-xtradb-cluster-operator created service/percona-xtradb-cluster-operator created pod/percona-xtradb-cluster-operator-55d95dc9d8-4jxgz condition met E0516 23:17:35.779072 2763 reflector.go:227] "Failed to watch" err="Get \"https://35.225.104.245/api/v1/namespaces/pxc-operator/pods?allowWatchBookmarks=true&fieldSelector=metadata.name%3Dpercona-xtradb-cluster-operator-55d95dc9d8-4jxgz&resourceVersion=1778973455417284000&timeoutSeconds=407&watch=true\": context canceled" reflector="k8s.io/client-go/tools/watch/informerwatcher.go:162" type="*unstructured.Unstructured" pod/percona-xtradb-cluster-operator-55d95dc9d8-4jxgz condition met E0516 23:17:43.507799 3872 reflector.go:227] "Failed to watch" err="Get \"https://35.225.104.245/api/v1/namespaces/pxc-operator/pods?allowWatchBookmarks=true&fieldSelector=metadata.name%3Dpercona-xtradb-cluster-operator-55d95dc9d8-4jxgz&resourceVersion=1778973460814140000&timeoutSeconds=498&watch=true\": context canceled" reflector="k8s.io/client-go/tools/watch/informerwatcher.go:162" type="*unstructured.Unstructured" waiting for pod/percona-xtradb-cluster-operator-55d95dc9d8-4jxgz to become Ready.Ok 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-flow-control-22777 ----------------------------------------------------------------------------------- Error from server (NotFound): namespaces "demand-backup-flow-control-22777" not found waiting for namespace/demand-backup-flow-control-22777 to be deletederror: resource(s) were provided, but no name was specified Error from server (NotFound): namespaces "demand-backup-flow-control-22777" not found ----------------------------------------------------------------------------------- create namespace demand-backup-flow-control-22777 ----------------------------------------------------------------------------------- namespace/demand-backup-flow-control-22777 created Context "gke_cloud-dev-112233_us-central1-a_jen-pxc-2473-6d392bea-4-cluster6" modified. ----------------------------------------------------------------------------------- create secrets for cloud storages ----------------------------------------------------------------------------------- secret/minio-secret created secret/aws-s3-secret created secret/do-spaces-secret created secret/gcp-cs-secret created secret/azure-secret created "hashicorp" already exists with the same configuration, skipping "minio" already exists with the same configuration, skipping Hang tight while we grab the latest from your chart repositories... ...Successfully got an update from the "minio" chart repository ...Successfully got an update from the "chaos-mesh" chart repository ...Successfully got an update from the "hashicorp" chart repository ...Successfully got an update from the "percona" chart repository Update Complete. ⎈Happy Helming!⎈ ----------------------------------------------------------------------------------- install Minio ----------------------------------------------------------------------------------- Error: uninstall: Release not loaded: minio-service: release: not found NAME: minio-service LAST DEPLOYED: Sat May 16 23:18:29 2026 NAMESPACE: demand-backup-flow-control-22777 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-flow-control-22777.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace demand-backup-flow-control-22777 -l "release=minio-service" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace demand-backup-flow-control-22777 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-flow-control-22777 minio-service -o jsonpath="{.data.rootUser}" | base64 --decode):$(kubectl get secret --namespace demand-backup-flow-control-22777 minio-service -o jsonpath="{.data.rootPassword}" | base64 --decode)@localhost:9000 3. mc ls minio-service-local pod/minio-service-5fd5489bdc-nh9t6 condition met E0516 23:19:31.155170 18616 reflector.go:227] "Failed to watch" err="Get \"https://35.225.104.245/api/v1/namespaces/demand-backup-flow-control-22777/pods?allowWatchBookmarks=true&fieldSelector=metadata.name%3Dminio-service-5fd5489bdc-nh9t6&resourceVersion=1778973569460180000&timeoutSeconds=530&watch=true\": context canceled" reflector="k8s.io/client-go/tools/watch/informerwatcher.go:162" type="*unstructured.Unstructured" waiting for pod/minio-service-5fd5489bdc-nh9t6 to become Ready.Ok make_bucket: operator-testing make_bucket: operator-testing pod "aws-cli" deleted from demand-backup-flow-control-22777 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-flow-control-22777 [2026-05-16T23:19:43+0000] creating PXC client deployment.apps/pxc-client created [2026-05-16T23:19:45+0000] creating cluster secrets secret/my-cluster-secrets created secret/some-name-ssl created secret/some-name-ssl-internal created [2026-05-16T23:19:49+0000] create PXC cluster: some-name perconaxtradbcluster.pxc.percona.com/some-name created ----------------------------------------------------------------------------------- wait cluster consistency ----------------------------------------------------------------------------------- waiting for pxc/some-name to be ready................................... ----------------------------------------------------------------------------------- CASE 1: startingDeadlineSeconds ----------------------------------------------------------------------------------- [2026-05-16T23:24:19+0000] setting startingDeadlineSeconds to 20 perconaxtradbcluster.pxc.percona.com/some-name patched [2026-05-16T23:24:22+0000] create dummy lock to block backup lease.coordination.k8s.io/pxc-some-name-backup-lock created [2026-05-16T23:24:24+0000] creating pxc-backup/backup1 perconaxtradbclusterbackup.pxc.percona.com/backup1 created waiting for pxc-backup/backup1 to reach Failed state......Failed [2026-05-16T23:24:47+0000] operator should fail backup starting deadline seconds exceeded: deadline exceeded [2026-05-16T23:24:50+0000] operator successfully failed the backup job lease.coordination.k8s.io "pxc-some-name-backup-lock" deleted from demand-backup-flow-control-22777 namespace ----------------------------------------------------------------------------------- CASE 1: startingDeadlineSeconds PASSED ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- CASE 2: suspend and resume ----------------------------------------------------------------------------------- [2026-05-16T23:24:52+0000] setting suspendedDeadlineSeconds to 300 perconaxtradbcluster.pxc.percona.com/some-name patched [2026-05-16T23:24:56+0000] creating pxc-backup/backup2 perconaxtradbclusterbackup.pxc.percona.com/backup2 created waiting for pxc-backup/backup2 to reach Running state......Running [2026-05-16T23:25:25+0000] deleting pod/some-name-pxc-2 pod "some-name-pxc-2" force deleted from demand-backup-flow-control-22777 namespace Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. waiting for pxc-backup/backup2 to reach Suspended stateSuspended ----------------------------------------------------------------------------------- wait cluster consistency ----------------------------------------------------------------------------------- waiting for pxc/some-name to be ready....... waiting for pxc-backup/backup2 to reach Succeeded state........................Succeeded ----------------------------------------------------------------------------------- CASE 2: suspend and resume PASSED ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- CASE 3: suspendedDeadlineSeconds ----------------------------------------------------------------------------------- [2026-05-16T23:27:31+0000] setting suspendedDeadlineSeconds to 10 perconaxtradbcluster.pxc.percona.com/some-name patched [2026-05-16T23:27:33+0000] creating pxc-backup/backup3 perconaxtradbclusterbackup.pxc.percona.com/backup3 created waiting for pxc-backup/backup3 to reach Running state..Running [2026-05-16T23:27:41+0000] deleting pod/some-name-pxc-2 pod "some-name-pxc-2" force deleted from demand-backup-flow-control-22777 namespace Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. waiting for pxc-backup/backup3 to reach Suspended state.....Suspended ----------------------------------------------------------------------------------- wait cluster consistency ----------------------------------------------------------------------------------- waiting for pxc/some-name to be ready..... waiting for pxc-backup/backup3 to reach Failed stateFailed [2026-05-16T23:28:42+0000] operator should fail backup suspended deadline seconds exceeded: deadline exceeded ----------------------------------------------------------------------------------- CASE 3: suspendedDeadlineSeconds PASSED ----------------------------------------------------------------------------------- [2026-05-16T23:28:44+0000] test passed ----------------------------------------------------------------------------------- destroy cluster/operator and all other resources ----------------------------------------------------------------------------------- + kubectl patch pxc -n demand-backup-flow-control-22777 some-name --type=merge -p '{"metadata":{"finalizers":[]}}' perconaxtradbcluster.pxc.percona.com/some-name patched perconaxtradbcluster.pxc.percona.com "some-name" deleted from demand-backup-flow-control-22777 namespace perconaxtradbclusterbackup.pxc.percona.com "backup1" deleted from demand-backup-flow-control-22777 namespace perconaxtradbclusterbackup.pxc.percona.com "backup2" deleted from demand-backup-flow-control-22777 namespace perconaxtradbclusterbackup.pxc.percona.com "backup3" deleted from demand-backup-flow-control-22777 namespace No resources found validatingwebhookconfiguration.admissionregistration.k8s.io "percona-xtradbcluster-webhook" deleted