Recent runs || View in Spyglass
PR | CecileRobertMichon: Switch flavor and test templates to external cloud-provider |
Result | FAILURE |
Tests | 6 failed / 21 succeeded |
Started | |
Elapsed | 50m53s |
Revision | 65957cf999e471834699d80bd2d98beb33399003 |
Refs |
3105 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sWorkload\scluster\screation\sCreating\sa\sFlatcar\scluster\s\[OPTIONAL\]\sWith\sFlatcar\scontrol\-plane\sand\sworker\snodes$'
[FAILED] Timed out after 1200.001s. No Control Plane machines came into existence. Expected <bool>: false to be true In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:05:57.443from junit.e2e_suite.1.xml
2023/01/27 00:38:58 failed trying to get namespace (capz-e2e-j4x3j4):namespaces "capz-e2e-j4x3j4" not found cluster.cluster.x-k8s.io/capz-e2e-j4x3j4-flatcar created azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-j4x3j4-flatcar created kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-j4x3j4-flatcar-control-plane created azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-j4x3j4-flatcar-control-plane created machinedeployment.cluster.x-k8s.io/capz-e2e-j4x3j4-flatcar-md-0 created azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-j4x3j4-flatcar-md-0 created kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-j4x3j4-flatcar-md-0 created azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created felixconfiguration.crd.projectcalico.org/default configured Failed to get logs for Machine capz-e2e-j4x3j4-flatcar-control-plane-4tjwz, Cluster capz-e2e-j4x3j4/capz-e2e-j4x3j4-flatcar: [dialing public load balancer at capz-e2e-j4x3j4-flatcar-2f7c516d.eastus.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.3.153:45508->20.232.250.218:22: read: connection reset by peer, dialing public load balancer at capz-e2e-j4x3j4-flatcar-2f7c516d.eastus.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.3.153:45512->20.232.250.218:22: read: connection reset by peer] Failed to get logs for Machine capz-e2e-j4x3j4-flatcar-md-0-56c45485b8-wc248, Cluster capz-e2e-j4x3j4/capz-e2e-j4x3j4-flatcar: [dialing public load balancer at capz-e2e-j4x3j4-flatcar-2f7c516d.eastus.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.3.153:56296->20.232.250.218:22: read: connection reset by peer, dialing public load balancer at capz-e2e-j4x3j4-flatcar-2f7c516d.eastus.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.3.153:56304->20.232.250.218:22: read: connection reset by peer, dialing public load balancer at capz-e2e-j4x3j4-flatcar-2f7c516d.eastus.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.3.153:56288->20.232.250.218:22: read: connection reset by peer, dialing public load balancer at capz-e2e-j4x3j4-flatcar-2f7c516d.eastus.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.3.153:56298->20.232.250.218:22: read: connection reset by peer, dialing public load balancer at capz-e2e-j4x3j4-flatcar-2f7c516d.eastus.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.3.153:56300->20.232.250.218:22: read: connection reset by peer, dialing public load balancer at capz-e2e-j4x3j4-flatcar-2f7c516d.eastus.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.3.153:56292->20.232.250.218:22: read: connection reset by peer, dialing public load balancer at capz-e2e-j4x3j4-flatcar-2f7c516d.eastus.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.3.153:56290->20.232.250.218:22: read: connection reset by peer, dialing public load balancer at capz-e2e-j4x3j4-flatcar-2f7c516d.eastus.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.3.153:56294->20.232.250.218:22: read: connection reset by peer, dialing public load balancer at capz-e2e-j4x3j4-flatcar-2f7c516d.eastus.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.3.153:56302->20.232.250.218:22: read: connection reset by peer] > Enter [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.371 INFO: "" started at Fri, 27 Jan 2023 00:38:58 UTC on Ginkgo node 2 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml STEP: Creating namespace "capz-e2e-j4x3j4" for hosting the cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:38:58.372 Jan 27 00:38:58.372: INFO: starting to create namespace for hosting the "capz-e2e-j4x3j4" test spec INFO: Creating namespace capz-e2e-j4x3j4 INFO: Creating event watcher for namespace "capz-e2e-j4x3j4" Jan 27 00:38:58.513: INFO: Creating cluster identity secret "cluster-identity-secret" < Exit [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.616 (244ms) > Enter [It] With Flatcar control-plane and worker nodes - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:321 @ 01/27/23 00:38:58.616 INFO: Cluster name is capz-e2e-j4x3j4-flatcar INFO: Creating the workload cluster with name "capz-e2e-j4x3j4-flatcar" using the "flatcar" template (Kubernetes v1.24.9, 1 control-plane machines, 1 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-e2e-j4x3j4-flatcar --infrastructure (default) --kubernetes-version v1.24.9 --control-plane-machine-count 1 --worker-machine-count 1 --flavor flatcar INFO: Applying the cluster template yaml to the cluster INFO: Waiting for the cluster infrastructure to be provisioned STEP: Waiting for cluster to enter the provisioned phase - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/cluster_helpers.go:134 @ 01/27/23 00:39:02.282 INFO: Waiting for control plane to be initialized STEP: Installing cloud-provider-azure components via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:45 @ 01/27/23 00:40:52.368 Jan 27 00:44:12.541: INFO: getting history for release cloud-provider-azure-oot Jan 27 00:44:12.571: INFO: Release cloud-provider-azure-oot does not exist, installing it Jan 27 00:44:14.036: INFO: creating 1 resource(s) Jan 27 00:44:14.116: INFO: creating 10 resource(s) Jan 27 00:44:14.402: INFO: Install complete STEP: Installing Calico CNI via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:51 @ 01/27/23 00:44:14.402 STEP: Configuring calico CNI helm chart for IPv4 configuration - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:112 @ 01/27/23 00:44:14.402 Jan 27 00:44:14.447: INFO: getting history for release projectcalico Jan 27 00:44:14.480: INFO: Release projectcalico does not exist, installing it Jan 27 00:44:15.029: INFO: creating 1 resource(s) Jan 27 00:44:15.075: INFO: creating 1 resource(s) Jan 27 00:44:15.116: INFO: creating 1 resource(s) Jan 27 00:44:15.155: INFO: creating 1 resource(s) Jan 27 00:44:15.210: INFO: creating 1 resource(s) Jan 27 00:44:15.258: INFO: creating 1 resource(s) Jan 27 00:44:15.342: INFO: creating 1 resource(s) Jan 27 00:44:15.498: INFO: creating 1 resource(s) Jan 27 00:44:15.776: INFO: creating 1 resource(s) Jan 27 00:44:15.820: INFO: creating 1 resource(s) Jan 27 00:44:15.876: INFO: creating 1 resource(s) Jan 27 00:44:15.916: INFO: creating 1 resource(s) Jan 27 00:44:15.961: INFO: creating 1 resource(s) Jan 27 00:44:16.003: INFO: creating 1 resource(s) Jan 27 00:44:16.045: INFO: creating 1 resource(s) Jan 27 00:44:16.098: INFO: creating 1 resource(s) Jan 27 00:44:16.182: INFO: creating 1 resource(s) Jan 27 00:44:16.231: INFO: creating 1 resource(s) Jan 27 00:44:16.292: INFO: creating 1 resource(s) Jan 27 00:44:16.405: INFO: creating 1 resource(s) Jan 27 00:44:16.652: INFO: creating 1 resource(s) Jan 27 00:44:16.750: INFO: Clearing discovery cache Jan 27 00:44:16.750: INFO: beginning wait for 21 resources with timeout of 1m0s Jan 27 00:44:19.038: INFO: creating 1 resource(s) Jan 27 00:44:19.504: INFO: creating 6 resource(s) Jan 27 00:44:20.111: INFO: Install complete STEP: Waiting for Ready tigera-operator deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:60 @ 01/27/23 00:44:20.348 STEP: waiting for deployment tigera-operator/tigera-operator to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:44:20.468 Jan 27 00:44:20.468: INFO: starting to wait for deployment to become available Jan 27 00:44:30.529: INFO: Deployment tigera-operator/tigera-operator is now available, took 10.060439698s STEP: Waiting for Ready calico-system deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:74 @ 01/27/23 00:44:35.12 STEP: waiting for deployment calico-system/calico-kube-controllers to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:44:35.264 Jan 27 00:44:35.264: INFO: starting to wait for deployment to become available Jan 27 00:45:16.386: INFO: Deployment calico-system/calico-kube-controllers is now available, took 41.122064993s STEP: waiting for deployment calico-system/calico-typha to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:45:16.758 Jan 27 00:45:16.758: INFO: starting to wait for deployment to become available Jan 27 00:45:16.829: INFO: Deployment calico-system/calico-typha is now available, took 70.993831ms STEP: Waiting for Ready calico-apiserver deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:79 @ 01/27/23 00:45:16.829 STEP: waiting for deployment calico-apiserver/calico-apiserver to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:45:17.054 Jan 27 00:45:17.054: INFO: starting to wait for deployment to become available Jan 27 00:45:37.145: INFO: Deployment calico-apiserver/calico-apiserver is now available, took 20.090908513s STEP: Waiting for Ready cloud-controller-manager deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:55 @ 01/27/23 00:45:37.162 STEP: waiting for deployment kube-system/cloud-controller-manager to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:45:37.335 Jan 27 00:45:37.335: INFO: starting to wait for deployment to become available Jan 27 00:45:57.424: INFO: Deployment kube-system/cloud-controller-manager is now available, took 20.08841908s INFO: Waiting for the first control plane machine managed by capz-e2e-j4x3j4/capz-e2e-j4x3j4-flatcar-control-plane to be provisioned STEP: Waiting for one control plane node to exist - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:133 @ 01/27/23 00:45:57.442 [FAILED] Timed out after 1200.001s. No Control Plane machines came into existence. Expected <bool>: false to be true In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:05:57.443 < Exit [It] With Flatcar control-plane and worker nodes - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:321 @ 01/27/23 01:05:57.443 (26m58.827s) > Enter [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:05:57.443 Jan 27 01:05:57.443: INFO: FAILED! Jan 27 01:05:57.443: INFO: Cleaning up after "Workload cluster creation Creating a Flatcar cluster [OPTIONAL] With Flatcar control-plane and worker nodes" spec STEP: Dumping logs from the "capz-e2e-j4x3j4-flatcar" workload cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 01:05:57.443 Jan 27 01:05:57.443: INFO: Dumping workload cluster capz-e2e-j4x3j4/capz-e2e-j4x3j4-flatcar logs Jan 27 01:05:57.492: INFO: Collecting logs for Linux node capz-e2e-j4x3j4-flatcar-control-plane-5b9gj in cluster capz-e2e-j4x3j4-flatcar in namespace capz-e2e-j4x3j4 Jan 27 01:06:58.706: INFO: Collecting boot logs for AzureMachine capz-e2e-j4x3j4-flatcar-control-plane-5b9gj Jan 27 01:06:59.868: INFO: Collecting logs for Linux node capz-e2e-j4x3j4-flatcar-md-0-x49mg in cluster capz-e2e-j4x3j4-flatcar in namespace capz-e2e-j4x3j4 Jan 27 01:08:00.184: INFO: Collecting boot logs for AzureMachine capz-e2e-j4x3j4-flatcar-md-0-x49mg Jan 27 01:08:00.658: INFO: Dumping workload cluster capz-e2e-j4x3j4/capz-e2e-j4x3j4-flatcar kube-system pod logs Jan 27 01:08:01.057: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-789ff4cbd9-npn2l, container calico-apiserver Jan 27 01:08:01.058: INFO: Describing Pod calico-apiserver/calico-apiserver-789ff4cbd9-npn2l Jan 27 01:08:01.113: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-789ff4cbd9-qdjz2, container calico-apiserver Jan 27 01:08:01.113: INFO: Describing Pod calico-apiserver/calico-apiserver-789ff4cbd9-qdjz2 Jan 27 01:08:01.170: INFO: Creating log watcher for controller calico-system/calico-kube-controllers-594d54f99-kmllv, container calico-kube-controllers Jan 27 01:08:01.177: INFO: Describing Pod calico-system/calico-kube-controllers-594d54f99-kmllv Jan 27 01:08:01.228: INFO: Creating log watcher for controller calico-system/calico-node-rrvp9, container calico-node Jan 27 01:08:01.228: INFO: Describing Pod calico-system/calico-node-rrvp9 Jan 27 01:08:01.292: INFO: Creating log watcher for controller calico-system/calico-node-vr4x2, container calico-node Jan 27 01:08:01.292: INFO: Describing Pod calico-system/calico-node-vr4x2 Jan 27 01:08:01.428: INFO: Describing Pod calico-system/calico-typha-549cc5bbdb-472sw Jan 27 01:08:01.428: INFO: Creating log watcher for controller calico-system/calico-typha-549cc5bbdb-472sw, container calico-typha Jan 27 01:08:01.830: INFO: Creating log watcher for controller calico-system/csi-node-driver-2xcg8, container csi-node-driver-registrar Jan 27 01:08:01.830: INFO: Creating log watcher for controller calico-system/csi-node-driver-2xcg8, container calico-csi Jan 27 01:08:01.830: INFO: Describing Pod calico-system/csi-node-driver-2xcg8 Jan 27 01:08:02.229: INFO: Describing Pod calico-system/csi-node-driver-sqrvf Jan 27 01:08:02.229: INFO: Creating log watcher for controller calico-system/csi-node-driver-sqrvf, container calico-csi Jan 27 01:08:02.229: INFO: Creating log watcher for controller calico-system/csi-node-driver-sqrvf, container csi-node-driver-registrar Jan 27 01:08:02.629: INFO: Describing Pod kube-system/cloud-controller-manager-865b6ddcfd-wlrx9 Jan 27 01:08:02.629: INFO: Creating log watcher for controller kube-system/cloud-controller-manager-865b6ddcfd-wlrx9, container cloud-controller-manager Jan 27 01:08:03.028: INFO: Describing Pod kube-system/cloud-node-manager-f46ks Jan 27 01:08:03.028: INFO: Creating log watcher for controller kube-system/cloud-node-manager-f46ks, container cloud-node-manager Jan 27 01:08:03.429: INFO: Describing Pod kube-system/cloud-node-manager-gwv7h Jan 27 01:08:03.429: INFO: Creating log watcher for controller kube-system/cloud-node-manager-gwv7h, container cloud-node-manager Jan 27 01:08:03.829: INFO: Describing Pod kube-system/coredns-57575c5f89-bb2hl Jan 27 01:08:03.829: INFO: Creating log watcher for controller kube-system/coredns-57575c5f89-bb2hl, container coredns Jan 27 01:08:04.229: INFO: Describing Pod kube-system/coredns-57575c5f89-nqf9h Jan 27 01:08:04.229: INFO: Creating log watcher for controller kube-system/coredns-57575c5f89-nqf9h, container coredns Jan 27 01:08:04.628: INFO: Creating log watcher for controller kube-system/etcd-capz-e2e-j4x3j4-flatcar-control-plane-5b9gj, container etcd Jan 27 01:08:04.628: INFO: Describing Pod kube-system/etcd-capz-e2e-j4x3j4-flatcar-control-plane-5b9gj Jan 27 01:08:05.033: INFO: Describing Pod kube-system/kube-apiserver-capz-e2e-j4x3j4-flatcar-control-plane-5b9gj Jan 27 01:08:05.033: INFO: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-j4x3j4-flatcar-control-plane-5b9gj, container kube-apiserver Jan 27 01:08:05.429: INFO: Describing Pod kube-system/kube-controller-manager-capz-e2e-j4x3j4-flatcar-control-plane-5b9gj Jan 27 01:08:05.429: INFO: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-j4x3j4-flatcar-control-plane-5b9gj, container kube-controller-manager Jan 27 01:08:05.829: INFO: Creating log watcher for controller kube-system/kube-proxy-lbk24, container kube-proxy Jan 27 01:08:05.829: INFO: Describing Pod kube-system/kube-proxy-lbk24 Jan 27 01:08:06.229: INFO: Creating log watcher for controller kube-system/kube-proxy-rclxb, container kube-proxy Jan 27 01:08:06.229: INFO: Describing Pod kube-system/kube-proxy-rclxb Jan 27 01:08:06.628: INFO: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-j4x3j4-flatcar-control-plane-5b9gj, container kube-scheduler Jan 27 01:08:06.628: INFO: Describing Pod kube-system/kube-scheduler-capz-e2e-j4x3j4-flatcar-control-plane-5b9gj Jan 27 01:08:07.028: INFO: Fetching kube-system pod logs took 6.369551607s Jan 27 01:08:07.028: INFO: Dumping workload cluster capz-e2e-j4x3j4/capz-e2e-j4x3j4-flatcar Azure activity log Jan 27 01:08:07.028: INFO: Creating log watcher for controller tigera-operator/tigera-operator-65d6bf4d4f-mgngt, container tigera-operator Jan 27 01:08:07.028: INFO: Describing Pod tigera-operator/tigera-operator-65d6bf4d4f-mgngt Jan 27 01:08:11.654: INFO: Fetching activity logs took 4.625917983s Jan 27 01:08:11.654: INFO: Dumping all the Cluster API resources in the "capz-e2e-j4x3j4" namespace Jan 27 01:08:11.967: INFO: Deleting all clusters in the capz-e2e-j4x3j4 namespace STEP: Deleting cluster capz-e2e-j4x3j4-flatcar - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:08:11.985 INFO: Waiting for the Cluster capz-e2e-j4x3j4/capz-e2e-j4x3j4-flatcar to be deleted STEP: Waiting for cluster capz-e2e-j4x3j4-flatcar to be deleted - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:08:11.997 Jan 27 01:12:52.180: INFO: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace capz-e2e-j4x3j4 Jan 27 01:12:52.199: INFO: Checking if any resources are left over in Azure for spec "create-workload-cluster" STEP: Redacting sensitive information from logs - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:216 @ 01/27/23 01:12:52.786 INFO: "With Flatcar control-plane and worker nodes" started at Fri, 27 Jan 2023 01:14:09 UTC on Ginkgo node 2 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml < Exit [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:14:09.832 (8m12.389s)
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sWorkload\scluster\screation\sCreating\sa\sGPU\-enabled\scluster\s\[OPTIONAL\]\swith\sa\ssingle\scontrol\splane\snode\sand\s1\snode$'
[FAILED] Timed out after 1200.000s. No Control Plane machines came into existence. Expected <bool>: false to be true In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:06:03.204from junit.e2e_suite.1.xml
2023/01/27 00:38:58 failed trying to get namespace (capz-e2e-3fq69z):namespaces "capz-e2e-3fq69z" not found cluster.cluster.x-k8s.io/capz-e2e-3fq69z-gpu serverside-applied azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-3fq69z-gpu serverside-applied kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-3fq69z-gpu-control-plane serverside-applied azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-3fq69z-gpu-control-plane serverside-applied azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp serverside-applied machinedeployment.cluster.x-k8s.io/capz-e2e-3fq69z-gpu-md-0 serverside-applied azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-3fq69z-gpu-md-0 serverside-applied kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-3fq69z-gpu-md-0 serverside-applied clusterresourceset.addons.cluster.x-k8s.io/crs-gpu-operator serverside-applied configmap/nvidia-clusterpolicy-crd serverside-applied configmap/nvidia-gpu-operator-components serverside-applied felixconfiguration.crd.projectcalico.org/default configured > Enter [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.372 INFO: "" started at Fri, 27 Jan 2023 00:38:58 UTC on Ginkgo node 3 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml STEP: Creating namespace "capz-e2e-3fq69z" for hosting the cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:38:58.372 Jan 27 00:38:58.372: INFO: starting to create namespace for hosting the "capz-e2e-3fq69z" test spec INFO: Creating namespace capz-e2e-3fq69z INFO: Creating event watcher for namespace "capz-e2e-3fq69z" Jan 27 00:38:58.521: INFO: Using existing cluster identity secret < Exit [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.522 (150ms) > Enter [It] with a single control plane node and 1 node - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:506 @ 01/27/23 00:38:58.522 INFO: Cluster name is capz-e2e-3fq69z-gpu INFO: Creating the workload cluster with name "capz-e2e-3fq69z-gpu" using the "nvidia-gpu" template (Kubernetes v1.24.10, 1 control-plane machines, 1 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-e2e-3fq69z-gpu --infrastructure (default) --kubernetes-version v1.24.10 --control-plane-machine-count 1 --worker-machine-count 1 --flavor nvidia-gpu INFO: Applying the cluster template yaml to the cluster INFO: Waiting for the cluster infrastructure to be provisioned STEP: Waiting for cluster to enter the provisioned phase - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/cluster_helpers.go:134 @ 01/27/23 00:39:02.409 INFO: Waiting for control plane to be initialized STEP: Installing cloud-provider-azure components via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:45 @ 01/27/23 00:41:02.501 Jan 27 00:42:38.374: INFO: getting history for release cloud-provider-azure-oot Jan 27 00:42:38.554: INFO: Release cloud-provider-azure-oot does not exist, installing it Jan 27 00:42:42.270: INFO: creating 1 resource(s) Jan 27 00:42:42.501: INFO: creating 10 resource(s) Jan 27 00:42:43.286: INFO: Install complete STEP: Installing Calico CNI via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:51 @ 01/27/23 00:42:43.286 STEP: Configuring calico CNI helm chart for IPv4 configuration - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:112 @ 01/27/23 00:42:43.286 Jan 27 00:42:43.405: INFO: getting history for release projectcalico Jan 27 00:42:43.509: INFO: Release projectcalico does not exist, installing it Jan 27 00:42:44.265: INFO: creating 1 resource(s) Jan 27 00:42:44.388: INFO: creating 1 resource(s) Jan 27 00:42:44.507: INFO: creating 1 resource(s) Jan 27 00:42:44.625: INFO: creating 1 resource(s) Jan 27 00:42:44.748: INFO: creating 1 resource(s) Jan 27 00:42:44.874: INFO: creating 1 resource(s) Jan 27 00:42:45.115: INFO: creating 1 resource(s) Jan 27 00:42:45.250: INFO: creating 1 resource(s) Jan 27 00:42:45.473: INFO: creating 1 resource(s) Jan 27 00:42:45.597: INFO: creating 1 resource(s) Jan 27 00:42:45.714: INFO: creating 1 resource(s) Jan 27 00:42:45.831: INFO: creating 1 resource(s) Jan 27 00:42:45.949: INFO: creating 1 resource(s) Jan 27 00:42:46.069: INFO: creating 1 resource(s) Jan 27 00:42:46.200: INFO: creating 1 resource(s) Jan 27 00:42:46.338: INFO: creating 1 resource(s) Jan 27 00:42:46.469: INFO: creating 1 resource(s) Jan 27 00:42:46.588: INFO: creating 1 resource(s) Jan 27 00:42:46.732: INFO: creating 1 resource(s) Jan 27 00:42:46.928: INFO: creating 1 resource(s) Jan 27 00:42:47.482: INFO: creating 1 resource(s) Jan 27 00:42:47.594: INFO: Clearing discovery cache Jan 27 00:42:47.594: INFO: beginning wait for 21 resources with timeout of 1m0s Jan 27 00:42:52.775: INFO: creating 1 resource(s) Jan 27 00:42:53.582: INFO: creating 6 resource(s) Jan 27 00:42:54.713: INFO: Install complete STEP: Waiting for Ready tigera-operator deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:60 @ 01/27/23 00:42:55.489 STEP: waiting for deployment tigera-operator/tigera-operator to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:42:55.911 Jan 27 00:42:55.911: INFO: starting to wait for deployment to become available Jan 27 00:43:06.117: INFO: Deployment tigera-operator/tigera-operator is now available, took 10.206106244s STEP: Waiting for Ready calico-system deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:74 @ 01/27/23 00:43:08.396 STEP: waiting for deployment calico-system/calico-kube-controllers to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:43:08.913 Jan 27 00:43:08.913: INFO: starting to wait for deployment to become available Jan 27 00:45:00.429: INFO: Deployment calico-system/calico-kube-controllers is now available, took 1m51.516704124s STEP: waiting for deployment calico-system/calico-typha to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:45:00.969 Jan 27 00:45:00.969: INFO: starting to wait for deployment to become available Jan 27 00:45:01.075: INFO: Deployment calico-system/calico-typha is now available, took 106.255616ms STEP: Waiting for Ready calico-apiserver deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:79 @ 01/27/23 00:45:01.075 STEP: waiting for deployment calico-apiserver/calico-apiserver to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:45:31.903 Jan 27 00:45:31.903: INFO: starting to wait for deployment to become available Jan 27 00:46:02.427: INFO: Deployment calico-apiserver/calico-apiserver is now available, took 30.524566359s STEP: Waiting for Ready cloud-controller-manager deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:55 @ 01/27/23 00:46:02.453 STEP: waiting for deployment kube-system/cloud-controller-manager to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:46:03.076 Jan 27 00:46:03.076: INFO: starting to wait for deployment to become available Jan 27 00:46:03.185: INFO: Deployment kube-system/cloud-controller-manager is now available, took 108.346201ms INFO: Waiting for the first control plane machine managed by capz-e2e-3fq69z/capz-e2e-3fq69z-gpu-control-plane to be provisioned STEP: Waiting for one control plane node to exist - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:133 @ 01/27/23 00:46:03.203 [FAILED] Timed out after 1200.000s. No Control Plane machines came into existence. Expected <bool>: false to be true In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:06:03.204 < Exit [It] with a single control plane node and 1 node - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:506 @ 01/27/23 01:06:03.204 (27m4.683s) > Enter [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:06:03.204 Jan 27 01:06:03.204: INFO: FAILED! Jan 27 01:06:03.204: INFO: Cleaning up after "Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node" spec STEP: Dumping logs from the "capz-e2e-3fq69z-gpu" workload cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 01:06:03.204 Jan 27 01:06:03.204: INFO: Dumping workload cluster capz-e2e-3fq69z/capz-e2e-3fq69z-gpu logs Jan 27 01:06:03.254: INFO: Collecting logs for Linux node capz-e2e-3fq69z-gpu-control-plane-2ws7l in cluster capz-e2e-3fq69z-gpu in namespace capz-e2e-3fq69z Jan 27 01:06:24.539: INFO: Collecting boot logs for AzureMachine capz-e2e-3fq69z-gpu-control-plane-2ws7l Jan 27 01:06:25.956: INFO: Collecting logs for Linux node capz-e2e-3fq69z-gpu-md-0-lgzlf in cluster capz-e2e-3fq69z-gpu in namespace capz-e2e-3fq69z Jan 27 01:07:13.493: INFO: Collecting boot logs for AzureMachine capz-e2e-3fq69z-gpu-md-0-lgzlf Jan 27 01:07:14.561: INFO: Dumping workload cluster capz-e2e-3fq69z/capz-e2e-3fq69z-gpu kube-system pod logs Jan 27 01:07:15.706: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-8bb76fc6f-dwfbl, container calico-apiserver Jan 27 01:07:15.706: INFO: Describing Pod calico-apiserver/calico-apiserver-8bb76fc6f-dwfbl Jan 27 01:07:15.930: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-8bb76fc6f-k5hfk, container calico-apiserver Jan 27 01:07:15.930: INFO: Describing Pod calico-apiserver/calico-apiserver-8bb76fc6f-k5hfk Jan 27 01:07:16.154: INFO: Creating log watcher for controller calico-system/calico-kube-controllers-594d54f99-j9fsk, container calico-kube-controllers Jan 27 01:07:16.154: INFO: Describing Pod calico-system/calico-kube-controllers-594d54f99-j9fsk Jan 27 01:07:16.402: INFO: Creating log watcher for controller calico-system/calico-node-jhl7v, container calico-node Jan 27 01:07:16.402: INFO: Describing Pod calico-system/calico-node-jhl7v Jan 27 01:07:16.787: INFO: Creating log watcher for controller calico-system/calico-node-xdjlx, container calico-node Jan 27 01:07:16.787: INFO: Describing Pod calico-system/calico-node-xdjlx Jan 27 01:07:16.998: INFO: Creating log watcher for controller calico-system/calico-typha-6f5b849b84-pm2dw, container calico-typha Jan 27 01:07:16.998: INFO: Describing Pod calico-system/calico-typha-6f5b849b84-pm2dw Jan 27 01:07:17.229: INFO: Creating log watcher for controller calico-system/csi-node-driver-fb85n, container calico-csi Jan 27 01:07:17.229: INFO: Creating log watcher for controller calico-system/csi-node-driver-fb85n, container csi-node-driver-registrar Jan 27 01:07:17.229: INFO: Describing Pod calico-system/csi-node-driver-fb85n Jan 27 01:07:17.439: INFO: Creating log watcher for controller calico-system/csi-node-driver-srsnh, container calico-csi Jan 27 01:07:17.439: INFO: Creating log watcher for controller calico-system/csi-node-driver-srsnh, container csi-node-driver-registrar Jan 27 01:07:17.439: INFO: Describing Pod calico-system/csi-node-driver-srsnh Jan 27 01:07:17.653: INFO: Creating log watcher for controller gpu-operator-resources/gpu-feature-discovery-2v2jd, container gpu-feature-discovery Jan 27 01:07:17.653: INFO: Describing Pod gpu-operator-resources/gpu-feature-discovery-2v2jd Jan 27 01:07:17.863: INFO: Creating log watcher for controller gpu-operator-resources/gpu-operator-79c7dfc46c-lgmp8, container gpu-operator Jan 27 01:07:17.863: INFO: Describing Pod gpu-operator-resources/gpu-operator-79c7dfc46c-lgmp8 Jan 27 01:07:18.102: INFO: Creating log watcher for controller gpu-operator-resources/gpu-operator-node-feature-discovery-master-58fd98d466-jz6s2, container master Jan 27 01:07:18.102: INFO: Describing Pod gpu-operator-resources/gpu-operator-node-feature-discovery-master-58fd98d466-jz6s2 Jan 27 01:07:18.378: INFO: Creating log watcher for controller gpu-operator-resources/gpu-operator-node-feature-discovery-worker-cqr8n, container worker Jan 27 01:07:18.378: INFO: Describing Pod gpu-operator-resources/gpu-operator-node-feature-discovery-worker-cqr8n Jan 27 01:07:18.780: INFO: Creating log watcher for controller gpu-operator-resources/gpu-operator-node-feature-discovery-worker-lnzdq, container worker Jan 27 01:07:18.780: INFO: Describing Pod gpu-operator-resources/gpu-operator-node-feature-discovery-worker-lnzdq Jan 27 01:07:19.177: INFO: Describing Pod gpu-operator-resources/nvidia-container-toolkit-daemonset-bf72f Jan 27 01:07:19.177: INFO: Creating log watcher for controller gpu-operator-resources/nvidia-container-toolkit-daemonset-bf72f, container nvidia-container-toolkit-ctr Jan 27 01:07:19.583: INFO: Describing Pod gpu-operator-resources/nvidia-cuda-validator-ddbxg Jan 27 01:07:19.583: INFO: Creating log watcher for controller gpu-operator-resources/nvidia-cuda-validator-ddbxg, container nvidia-cuda-validator Jan 27 01:07:19.977: INFO: Describing Pod gpu-operator-resources/nvidia-dcgm-exporter-9sk5s Jan 27 01:07:19.977: INFO: Creating log watcher for controller gpu-operator-resources/nvidia-dcgm-exporter-9sk5s, container nvidia-dcgm-exporter Jan 27 01:07:20.378: INFO: Describing Pod gpu-operator-resources/nvidia-device-plugin-daemonset-r7skr Jan 27 01:07:20.378: INFO: Creating log watcher for controller gpu-operator-resources/nvidia-device-plugin-daemonset-r7skr, container nvidia-device-plugin-ctr Jan 27 01:07:20.778: INFO: Creating log watcher for controller gpu-operator-resources/nvidia-device-plugin-validator-jpgzb, container nvidia-device-plugin-validator Jan 27 01:07:20.778: INFO: Describing Pod gpu-operator-resources/nvidia-device-plugin-validator-jpgzb Jan 27 01:07:21.178: INFO: Describing Pod gpu-operator-resources/nvidia-driver-daemonset-ws6lx Jan 27 01:07:21.178: INFO: Creating log watcher for controller gpu-operator-resources/nvidia-driver-daemonset-ws6lx, container nvidia-driver-ctr Jan 27 01:07:21.577: INFO: Describing Pod gpu-operator-resources/nvidia-operator-validator-j44x2 Jan 27 01:07:21.577: INFO: Creating log watcher for controller gpu-operator-resources/nvidia-operator-validator-j44x2, container nvidia-operator-validator Jan 27 01:07:21.977: INFO: Creating log watcher for controller kube-system/cloud-controller-manager-8dccd589f-ckm6s, container cloud-controller-manager Jan 27 01:07:21.977: INFO: Describing Pod kube-system/cloud-controller-manager-8dccd589f-ckm6s Jan 27 01:07:22.376: INFO: Creating log watcher for controller kube-system/cloud-node-manager-jwgqx, container cloud-node-manager Jan 27 01:07:22.376: INFO: Describing Pod kube-system/cloud-node-manager-jwgqx Jan 27 01:07:22.777: INFO: Describing Pod kube-system/cloud-node-manager-lf5ft Jan 27 01:07:22.777: INFO: Creating log watcher for controller kube-system/cloud-node-manager-lf5ft, container cloud-node-manager Jan 27 01:07:23.176: INFO: Creating log watcher for controller kube-system/coredns-57575c5f89-bknfq, container coredns Jan 27 01:07:23.176: INFO: Describing Pod kube-system/coredns-57575c5f89-bknfq Jan 27 01:07:23.576: INFO: Describing Pod kube-system/coredns-57575c5f89-hltg4 Jan 27 01:07:23.576: INFO: Creating log watcher for controller kube-system/coredns-57575c5f89-hltg4, container coredns Jan 27 01:07:23.976: INFO: Describing Pod kube-system/etcd-capz-e2e-3fq69z-gpu-control-plane-2ws7l Jan 27 01:07:23.976: INFO: Creating log watcher for controller kube-system/etcd-capz-e2e-3fq69z-gpu-control-plane-2ws7l, container etcd Jan 27 01:07:24.375: INFO: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-3fq69z-gpu-control-plane-2ws7l, container kube-apiserver Jan 27 01:07:24.375: INFO: Describing Pod kube-system/kube-apiserver-capz-e2e-3fq69z-gpu-control-plane-2ws7l Jan 27 01:07:24.790: INFO: Describing Pod kube-system/kube-controller-manager-capz-e2e-3fq69z-gpu-control-plane-2ws7l Jan 27 01:07:24.790: INFO: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-3fq69z-gpu-control-plane-2ws7l, container kube-controller-manager Jan 27 01:07:25.176: INFO: Describing Pod kube-system/kube-proxy-j9mdm Jan 27 01:07:25.176: INFO: Creating log watcher for controller kube-system/kube-proxy-j9mdm, container kube-proxy Jan 27 01:07:25.576: INFO: Creating log watcher for controller kube-system/kube-proxy-kmbtn, container kube-proxy Jan 27 01:07:25.576: INFO: Describing Pod kube-system/kube-proxy-kmbtn Jan 27 01:07:25.975: INFO: Describing Pod kube-system/kube-scheduler-capz-e2e-3fq69z-gpu-control-plane-2ws7l Jan 27 01:07:25.975: INFO: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-3fq69z-gpu-control-plane-2ws7l, container kube-scheduler Jan 27 01:07:26.376: INFO: Fetching kube-system pod logs took 11.814573086s Jan 27 01:07:26.376: INFO: Dumping workload cluster capz-e2e-3fq69z/capz-e2e-3fq69z-gpu Azure activity log Jan 27 01:07:26.376: INFO: Creating log watcher for controller tigera-operator/tigera-operator-65d6bf4d4f-9w9hq, container tigera-operator Jan 27 01:07:26.377: INFO: Describing Pod tigera-operator/tigera-operator-65d6bf4d4f-9w9hq Jan 27 01:07:29.813: INFO: Fetching activity logs took 3.437187338s Jan 27 01:07:29.813: INFO: Dumping all the Cluster API resources in the "capz-e2e-3fq69z" namespace Jan 27 01:07:30.118: INFO: Deleting all clusters in the capz-e2e-3fq69z namespace STEP: Deleting cluster capz-e2e-3fq69z-gpu - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:07:30.138 INFO: Waiting for the Cluster capz-e2e-3fq69z/capz-e2e-3fq69z-gpu to be deleted STEP: Waiting for cluster capz-e2e-3fq69z-gpu to be deleted - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:07:30.147 Jan 27 01:14:20.408: INFO: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace capz-e2e-3fq69z Jan 27 01:14:20.428: INFO: Checking if any resources are left over in Azure for spec "create-workload-cluster" STEP: Redacting sensitive information from logs - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:216 @ 01/27/23 01:14:21.009 INFO: "with a single control plane node and 1 node" started at Fri, 27 Jan 2023 01:15:37 UTC on Ginkgo node 3 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml < Exit [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:15:37.822 (9m34.617s)
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sWorkload\scluster\screation\sCreating\sa\scluster\sthat\suses\sthe\sexternal\scloud\sprovider\sand\smachinepools\s\[OPTIONAL\]\swith\s1\scontrol\splane\snode\sand\s1\smachinepool$'
[FAILED] Timed out after 1200.000s. No Control Plane machines came into existence. Expected <bool>: false to be true In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:05:02.996from junit.e2e_suite.1.xml
2023/01/27 00:38:58 failed trying to get namespace (capz-e2e-lcqaon):namespaces "capz-e2e-lcqaon" not found cluster.cluster.x-k8s.io/capz-e2e-lcqaon-flex created azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-lcqaon-flex created kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-lcqaon-flex-control-plane created azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-lcqaon-flex-control-plane created machinepool.cluster.x-k8s.io/capz-e2e-lcqaon-flex-mp-0 created azuremachinepool.infrastructure.cluster.x-k8s.io/capz-e2e-lcqaon-flex-mp-0 created kubeadmconfig.bootstrap.cluster.x-k8s.io/capz-e2e-lcqaon-flex-mp-0 created azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created machinepool.cluster.x-k8s.io/capz-e2e-lcqaon-flex-mp-win created azuremachinepool.infrastructure.cluster.x-k8s.io/capz-e2e-lcqaon-flex-mp-win created kubeadmconfig.bootstrap.cluster.x-k8s.io/capz-e2e-lcqaon-flex-mp-win created clusterresourceset.addons.cluster.x-k8s.io/capz-e2e-lcqaon-flex-calico-windows created clusterresourceset.addons.cluster.x-k8s.io/csi-proxy created clusterresourceset.addons.cluster.x-k8s.io/containerd-logger-capz-e2e-lcqaon-flex created configmap/cni-capz-e2e-lcqaon-flex-calico-windows created configmap/csi-proxy-addon created configmap/containerd-logger-capz-e2e-lcqaon-flex created felixconfiguration.crd.projectcalico.org/default configured > Enter [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.375 INFO: "" started at Fri, 27 Jan 2023 00:38:58 UTC on Ginkgo node 5 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml STEP: Creating namespace "capz-e2e-lcqaon" for hosting the cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:38:58.375 Jan 27 00:38:58.375: INFO: starting to create namespace for hosting the "capz-e2e-lcqaon" test spec INFO: Creating namespace capz-e2e-lcqaon INFO: Creating event watcher for namespace "capz-e2e-lcqaon" Jan 27 00:38:58.484: INFO: Creating cluster identity secret "cluster-identity-secret" < Exit [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.553 (179ms) > Enter [It] with 1 control plane node and 1 machinepool - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:573 @ 01/27/23 00:38:58.553 STEP: using user-assigned identity - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:574 @ 01/27/23 00:38:58.553 INFO: Cluster name is capz-e2e-lcqaon-flex INFO: Creating the workload cluster with name "capz-e2e-lcqaon-flex" using the "machine-pool-flex" template (Kubernetes v1.26.0, 1 control-plane machines, 1 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-e2e-lcqaon-flex --infrastructure (default) --kubernetes-version v1.26.0 --control-plane-machine-count 1 --worker-machine-count 1 --flavor machine-pool-flex INFO: Applying the cluster template yaml to the cluster INFO: Waiting for the cluster infrastructure to be provisioned STEP: Waiting for cluster to enter the provisioned phase - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/cluster_helpers.go:134 @ 01/27/23 00:39:02.511 INFO: Waiting for control plane to be initialized STEP: Installing cloud-provider-azure components via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:45 @ 01/27/23 00:40:52.595 Jan 27 00:43:32.766: INFO: getting history for release cloud-provider-azure-oot Jan 27 00:43:32.796: INFO: Release cloud-provider-azure-oot does not exist, installing it Jan 27 00:43:34.445: INFO: creating 1 resource(s) Jan 27 00:43:34.521: INFO: creating 10 resource(s) Jan 27 00:43:34.793: INFO: Install complete STEP: Installing Calico CNI via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:51 @ 01/27/23 00:43:34.793 STEP: Configuring calico CNI helm chart for IPv4 configuration - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:112 @ 01/27/23 00:43:34.793 Jan 27 00:43:34.840: INFO: getting history for release projectcalico Jan 27 00:43:34.870: INFO: Release projectcalico does not exist, installing it Jan 27 00:43:35.480: INFO: creating 1 resource(s) Jan 27 00:43:35.528: INFO: creating 1 resource(s) Jan 27 00:43:35.586: INFO: creating 1 resource(s) Jan 27 00:43:35.625: INFO: creating 1 resource(s) Jan 27 00:43:35.673: INFO: creating 1 resource(s) Jan 27 00:43:35.716: INFO: creating 1 resource(s) Jan 27 00:43:35.795: INFO: creating 1 resource(s) Jan 27 00:43:35.860: INFO: creating 1 resource(s) Jan 27 00:43:35.902: INFO: creating 1 resource(s) Jan 27 00:43:35.956: INFO: creating 1 resource(s) Jan 27 00:43:35.999: INFO: creating 1 resource(s) Jan 27 00:43:36.042: INFO: creating 1 resource(s) Jan 27 00:43:36.081: INFO: creating 1 resource(s) Jan 27 00:43:36.121: INFO: creating 1 resource(s) Jan 27 00:43:36.167: INFO: creating 1 resource(s) Jan 27 00:43:36.213: INFO: creating 1 resource(s) Jan 27 00:43:36.330: INFO: creating 1 resource(s) Jan 27 00:43:36.385: INFO: creating 1 resource(s) Jan 27 00:43:36.439: INFO: creating 1 resource(s) Jan 27 00:43:36.553: INFO: creating 1 resource(s) Jan 27 00:43:36.862: INFO: creating 1 resource(s) Jan 27 00:43:36.902: INFO: Clearing discovery cache Jan 27 00:43:36.902: INFO: beginning wait for 21 resources with timeout of 1m0s Jan 27 00:43:39.766: INFO: creating 1 resource(s) Jan 27 00:43:40.161: INFO: creating 6 resource(s) Jan 27 00:43:40.731: INFO: Install complete STEP: Waiting for Ready tigera-operator deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:60 @ 01/27/23 00:43:40.966 STEP: waiting for deployment tigera-operator/tigera-operator to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:43:41.089 Jan 27 00:43:41.089: INFO: starting to wait for deployment to become available Jan 27 00:43:51.146: INFO: Deployment tigera-operator/tigera-operator is now available, took 10.056982083s STEP: Waiting for Ready calico-system deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:74 @ 01/27/23 00:43:51.676 STEP: waiting for deployment calico-system/calico-kube-controllers to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:43:51.827 Jan 27 00:43:51.827: INFO: starting to wait for deployment to become available Jan 27 00:44:42.158: INFO: Deployment calico-system/calico-kube-controllers is now available, took 50.3315156s STEP: waiting for deployment calico-system/calico-typha to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:44:42.418 Jan 27 00:44:42.418: INFO: starting to wait for deployment to become available Jan 27 00:44:42.446: INFO: Deployment calico-system/calico-typha is now available, took 28.622702ms STEP: Waiting for Ready calico-apiserver deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:79 @ 01/27/23 00:44:42.446 STEP: waiting for deployment calico-apiserver/calico-apiserver to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:44:42.657 Jan 27 00:44:42.657: INFO: starting to wait for deployment to become available Jan 27 00:45:02.772: INFO: Deployment calico-apiserver/calico-apiserver is now available, took 20.115062232s STEP: Waiting for Ready cloud-controller-manager deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:55 @ 01/27/23 00:45:02.791 STEP: waiting for deployment kube-system/cloud-controller-manager to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:45:02.933 Jan 27 00:45:02.933: INFO: starting to wait for deployment to become available Jan 27 00:45:02.972: INFO: Deployment kube-system/cloud-controller-manager is now available, took 38.783037ms INFO: Waiting for the first control plane machine managed by capz-e2e-lcqaon/capz-e2e-lcqaon-flex-control-plane to be provisioned STEP: Waiting for one control plane node to exist - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:133 @ 01/27/23 00:45:02.995 [FAILED] Timed out after 1200.000s. No Control Plane machines came into existence. Expected <bool>: false to be true In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:05:02.996 < Exit [It] with 1 control plane node and 1 machinepool - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:573 @ 01/27/23 01:05:02.996 (26m4.443s) > Enter [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:05:02.996 Jan 27 01:05:02.996: INFO: FAILED! Jan 27 01:05:02.996: INFO: Cleaning up after "Workload cluster creation Creating a cluster that uses the external cloud provider and machinepools [OPTIONAL] with 1 control plane node and 1 machinepool" spec STEP: Dumping logs from the "capz-e2e-lcqaon-flex" workload cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 01:05:02.996 Jan 27 01:05:02.996: INFO: Dumping workload cluster capz-e2e-lcqaon/capz-e2e-lcqaon-flex logs Jan 27 01:05:03.041: INFO: Collecting logs for Linux node capz-e2e-lcqaon-flex-control-plane-4rqlt in cluster capz-e2e-lcqaon-flex in namespace capz-e2e-lcqaon Jan 27 01:05:17.249: INFO: Collecting boot logs for AzureMachine capz-e2e-lcqaon-flex-control-plane-4rqlt Jan 27 01:05:18.370: INFO: Dumping workload cluster capz-e2e-lcqaon/capz-e2e-lcqaon-flex kube-system pod logs Jan 27 01:05:18.801: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-b9d77db89-5l7th, container calico-apiserver Jan 27 01:05:18.802: INFO: Describing Pod calico-apiserver/calico-apiserver-b9d77db89-5l7th Jan 27 01:05:18.867: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-b9d77db89-ckcxf, container calico-apiserver Jan 27 01:05:18.867: INFO: Describing Pod calico-apiserver/calico-apiserver-b9d77db89-ckcxf Jan 27 01:05:18.933: INFO: Creating log watcher for controller calico-system/calico-kube-controllers-6b7b9c649d-qg4nx, container calico-kube-controllers Jan 27 01:05:18.935: INFO: Describing Pod calico-system/calico-kube-controllers-6b7b9c649d-qg4nx Jan 27 01:05:19.004: INFO: Describing Pod calico-system/calico-node-24qzm Jan 27 01:05:19.004: INFO: Creating log watcher for controller calico-system/calico-node-24qzm, container calico-node Jan 27 01:05:19.090: INFO: Creating log watcher for controller calico-system/calico-node-554ds, container calico-node Jan 27 01:05:19.090: INFO: Describing Pod calico-system/calico-node-554ds Jan 27 01:05:19.167: INFO: Creating log watcher for controller calico-system/calico-typha-5dc78cbcbc-rggq7, container calico-typha Jan 27 01:05:19.168: INFO: Describing Pod calico-system/calico-typha-5dc78cbcbc-rggq7 Jan 27 01:05:19.569: INFO: Creating log watcher for controller calico-system/csi-node-driver-5xdbg, container calico-csi Jan 27 01:05:19.570: INFO: Describing Pod calico-system/csi-node-driver-5xdbg Jan 27 01:05:19.570: INFO: Creating log watcher for controller calico-system/csi-node-driver-5xdbg, container csi-node-driver-registrar Jan 27 01:05:19.969: INFO: Creating log watcher for controller calico-system/csi-node-driver-hgfgj, container csi-node-driver-registrar Jan 27 01:05:19.969: INFO: Describing Pod calico-system/csi-node-driver-hgfgj Jan 27 01:05:19.970: INFO: Creating log watcher for controller calico-system/csi-node-driver-hgfgj, container calico-csi Jan 27 01:05:20.368: INFO: Creating log watcher for controller kube-system/cloud-controller-manager-68c957d74c-7htkt, container cloud-controller-manager Jan 27 01:05:20.368: INFO: Describing Pod kube-system/cloud-controller-manager-68c957d74c-7htkt Jan 27 01:05:20.768: INFO: Describing Pod kube-system/cloud-node-manager-lvbrc Jan 27 01:05:20.768: INFO: Creating log watcher for controller kube-system/cloud-node-manager-lvbrc, container cloud-node-manager Jan 27 01:05:21.169: INFO: Creating log watcher for controller kube-system/cloud-node-manager-p86dk, container cloud-node-manager Jan 27 01:05:21.169: INFO: Describing Pod kube-system/cloud-node-manager-p86dk Jan 27 01:05:21.567: INFO: Describing Pod kube-system/coredns-787d4945fb-9clz6 Jan 27 01:05:21.567: INFO: Creating log watcher for controller kube-system/coredns-787d4945fb-9clz6, container coredns Jan 27 01:05:21.968: INFO: Describing Pod kube-system/coredns-787d4945fb-z4pxj Jan 27 01:05:21.968: INFO: Creating log watcher for controller kube-system/coredns-787d4945fb-z4pxj, container coredns Jan 27 01:05:22.368: INFO: Creating log watcher for controller kube-system/etcd-capz-e2e-lcqaon-flex-control-plane-4rqlt, container etcd Jan 27 01:05:22.368: INFO: Describing Pod kube-system/etcd-capz-e2e-lcqaon-flex-control-plane-4rqlt Jan 27 01:05:22.767: INFO: Describing Pod kube-system/kube-apiserver-capz-e2e-lcqaon-flex-control-plane-4rqlt Jan 27 01:05:22.767: INFO: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-lcqaon-flex-control-plane-4rqlt, container kube-apiserver Jan 27 01:05:23.168: INFO: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-lcqaon-flex-control-plane-4rqlt, container kube-controller-manager Jan 27 01:05:23.168: INFO: Describing Pod kube-system/kube-controller-manager-capz-e2e-lcqaon-flex-control-plane-4rqlt Jan 27 01:05:23.568: INFO: Describing Pod kube-system/kube-proxy-d2g6d Jan 27 01:05:23.568: INFO: Creating log watcher for controller kube-system/kube-proxy-d2g6d, container kube-proxy Jan 27 01:05:23.967: INFO: Describing Pod kube-system/kube-proxy-dnv8r Jan 27 01:05:23.967: INFO: Creating log watcher for controller kube-system/kube-proxy-dnv8r, container kube-proxy Jan 27 01:05:24.368: INFO: Describing Pod kube-system/kube-scheduler-capz-e2e-lcqaon-flex-control-plane-4rqlt Jan 27 01:05:24.368: INFO: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-lcqaon-flex-control-plane-4rqlt, container kube-scheduler Jan 27 01:05:24.767: INFO: Fetching kube-system pod logs took 6.396391013s Jan 27 01:05:24.767: INFO: Dumping workload cluster capz-e2e-lcqaon/capz-e2e-lcqaon-flex Azure activity log Jan 27 01:05:24.767: INFO: Creating log watcher for controller tigera-operator/tigera-operator-54b47459dd-jtm27, container tigera-operator Jan 27 01:05:24.767: INFO: Describing Pod tigera-operator/tigera-operator-54b47459dd-jtm27 Jan 27 01:05:28.599: INFO: Fetching activity logs took 3.832038577s Jan 27 01:05:28.599: INFO: Dumping all the Cluster API resources in the "capz-e2e-lcqaon" namespace Jan 27 01:05:29.178: INFO: Deleting all clusters in the capz-e2e-lcqaon namespace STEP: Deleting cluster capz-e2e-lcqaon-flex - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:05:29.199 INFO: Waiting for the Cluster capz-e2e-lcqaon/capz-e2e-lcqaon-flex to be deleted STEP: Waiting for cluster capz-e2e-lcqaon-flex to be deleted - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:05:29.21 Jan 27 01:09:59.357: INFO: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace capz-e2e-lcqaon Jan 27 01:09:59.373: INFO: Checking if any resources are left over in Azure for spec "create-workload-cluster" STEP: Redacting sensitive information from logs - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:216 @ 01/27/23 01:09:59.959 INFO: "with 1 control plane node and 1 machinepool" started at Fri, 27 Jan 2023 01:11:39 UTC on Ginkgo node 5 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml < Exit [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:11:39.778 (6m36.782s)
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sWorkload\scluster\screation\sCreating\sa\sdual\-stack\scluster\s\[OPTIONAL\]\sWith\sdual\-stack\sworker\snode$'
[FAILED] Timed out after 1800.001s. Expected success, but got an error: <*errors.withStack | 0xc001a8db18>: { error: <*errors.withMessage | 0xc0016cefc0>{ cause: <*errors.fundamental | 0xc001a8dae8>{ msg: "key \"2001:1234:5678:9a40::/58\" has no value", stack: [0x3498795, 0x349770b, 0x3497256, 0x349a8b9, 0x36410d1, 0x154c085, 0x154b57c, 0x196a29a, 0x196b657, 0x196864d, 0x3640d9b, 0x3630f09, 0x3634505, 0x2fef810, 0x36440a5, 0x194537b, 0x1959958, 0x14d9741], }, msg: "failed parsing --set data", }, stack: [0x349a8f6, 0x36410d1, 0x154c085, 0x154b57c, 0x196a29a, 0x196b657, 0x196864d, 0x3640d9b, 0x3630f09, 0x3634505, 0x2fef810, 0x36440a5, 0x194537b, 0x1959958, 0x14d9741], } failed parsing --set data: key "2001:1234:5678:9a40::/58" has no value In [It] at: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:985 @ 01/27/23 01:12:17.881from junit.e2e_suite.1.xml
2023/01/27 00:38:58 failed trying to get namespace (capz-e2e-kxootk):namespaces "capz-e2e-kxootk" not found cluster.cluster.x-k8s.io/capz-e2e-kxootk-dual-stack created azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-kxootk-dual-stack created kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-kxootk-dual-stack-control-plane created azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-kxootk-dual-stack-control-plane created azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created machinedeployment.cluster.x-k8s.io/capz-e2e-kxootk-dual-stack-md-0 created azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-kxootk-dual-stack-md-0 created kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-kxootk-dual-stack-md-0 created > Enter [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.405 INFO: "" started at Fri, 27 Jan 2023 00:38:58 UTC on Ginkgo node 10 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml STEP: Creating namespace "capz-e2e-kxootk" for hosting the cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:38:58.405 Jan 27 00:38:58.405: INFO: starting to create namespace for hosting the "capz-e2e-kxootk" test spec INFO: Creating namespace capz-e2e-kxootk INFO: Creating event watcher for namespace "capz-e2e-kxootk" Jan 27 00:38:58.568: INFO: Using existing cluster identity secret < Exit [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.568 (163ms) > Enter [It] With dual-stack worker node - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:828 @ 01/27/23 00:38:58.568 STEP: using user-assigned identity - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:829 @ 01/27/23 00:38:58.568 INFO: Cluster name is capz-e2e-kxootk-dual-stack INFO: Creating the workload cluster with name "capz-e2e-kxootk-dual-stack" using the "dual-stack" template (Kubernetes v1.24.10, 3 control-plane machines, 1 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-e2e-kxootk-dual-stack --infrastructure (default) --kubernetes-version v1.24.10 --control-plane-machine-count 3 --worker-machine-count 1 --flavor dual-stack INFO: Applying the cluster template yaml to the cluster INFO: Waiting for the cluster infrastructure to be provisioned STEP: Waiting for cluster to enter the provisioned phase - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/cluster_helpers.go:134 @ 01/27/23 00:39:02.28 INFO: Waiting for control plane to be initialized STEP: Installing cloud-provider-azure components via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:45 @ 01/27/23 00:40:42.358 Jan 27 00:42:17.850: INFO: getting history for release cloud-provider-azure-oot Jan 27 00:42:17.879: INFO: Release cloud-provider-azure-oot does not exist, installing it [FAILED] Timed out after 1800.001s. Expected success, but got an error: <*errors.withStack | 0xc001a8db18>: { error: <*errors.withMessage | 0xc0016cefc0>{ cause: <*errors.fundamental | 0xc001a8dae8>{ msg: "key \"2001:1234:5678:9a40::/58\" has no value", stack: [0x3498795, 0x349770b, 0x3497256, 0x349a8b9, 0x36410d1, 0x154c085, 0x154b57c, 0x196a29a, 0x196b657, 0x196864d, 0x3640d9b, 0x3630f09, 0x3634505, 0x2fef810, 0x36440a5, 0x194537b, 0x1959958, 0x14d9741], }, msg: "failed parsing --set data", }, stack: [0x349a8f6, 0x36410d1, 0x154c085, 0x154b57c, 0x196a29a, 0x196b657, 0x196864d, 0x3640d9b, 0x3630f09, 0x3634505, 0x2fef810, 0x36440a5, 0x194537b, 0x1959958, 0x14d9741], } failed parsing --set data: key "2001:1234:5678:9a40::/58" has no value In [It] at: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:985 @ 01/27/23 01:12:17.881 < Exit [It] With dual-stack worker node - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:828 @ 01/27/23 01:12:17.881 (33m19.312s) > Enter [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:12:17.881 Jan 27 01:12:17.881: INFO: FAILED! Jan 27 01:12:17.881: INFO: Cleaning up after "Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node" spec STEP: Dumping logs from the "capz-e2e-kxootk-dual-stack" workload cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 01:12:17.881 Jan 27 01:12:17.881: INFO: Dumping workload cluster capz-e2e-kxootk/capz-e2e-kxootk-dual-stack logs Jan 27 01:12:17.933: INFO: Collecting logs for Linux node capz-e2e-kxootk-dual-stack-control-plane-c89x7 in cluster capz-e2e-kxootk-dual-stack in namespace capz-e2e-kxootk Jan 27 01:12:24.955: INFO: Collecting boot logs for AzureMachine capz-e2e-kxootk-dual-stack-control-plane-c89x7 Jan 27 01:12:26.199: INFO: Collecting logs for Linux node capz-e2e-kxootk-dual-stack-md-0-7wqrl in cluster capz-e2e-kxootk-dual-stack in namespace capz-e2e-kxootk Jan 27 01:12:33.006: INFO: Collecting boot logs for AzureMachine capz-e2e-kxootk-dual-stack-md-0-7wqrl Jan 27 01:12:33.463: INFO: Dumping workload cluster capz-e2e-kxootk/capz-e2e-kxootk-dual-stack kube-system pod logs Jan 27 01:12:33.836: INFO: Creating log watcher for controller kube-system/coredns-57575c5f89-79dkw, container coredns Jan 27 01:12:33.836: INFO: Describing Pod kube-system/coredns-57575c5f89-79dkw Jan 27 01:12:33.896: INFO: Creating log watcher for controller kube-system/coredns-57575c5f89-v8gbl, container coredns Jan 27 01:12:33.897: INFO: Describing Pod kube-system/coredns-57575c5f89-v8gbl Jan 27 01:12:33.958: INFO: Creating log watcher for controller kube-system/etcd-capz-e2e-kxootk-dual-stack-control-plane-c89x7, container etcd Jan 27 01:12:33.958: INFO: Describing Pod kube-system/etcd-capz-e2e-kxootk-dual-stack-control-plane-c89x7 Jan 27 01:12:34.036: INFO: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-kxootk-dual-stack-control-plane-c89x7, container kube-apiserver Jan 27 01:12:34.036: INFO: Describing Pod kube-system/kube-apiserver-capz-e2e-kxootk-dual-stack-control-plane-c89x7 Jan 27 01:12:34.095: INFO: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-kxootk-dual-stack-control-plane-c89x7, container kube-controller-manager Jan 27 01:12:34.095: INFO: Describing Pod kube-system/kube-controller-manager-capz-e2e-kxootk-dual-stack-control-plane-c89x7 Jan 27 01:12:34.212: INFO: Describing Pod kube-system/kube-proxy-2zsdz Jan 27 01:12:34.212: INFO: Creating log watcher for controller kube-system/kube-proxy-2zsdz, container kube-proxy Jan 27 01:12:34.604: INFO: Creating log watcher for controller kube-system/kube-proxy-x4ncv, container kube-proxy Jan 27 01:12:34.604: INFO: Describing Pod kube-system/kube-proxy-x4ncv Jan 27 01:12:35.004: INFO: Fetching kube-system pod logs took 1.54105646s Jan 27 01:12:35.004: INFO: Dumping workload cluster capz-e2e-kxootk/capz-e2e-kxootk-dual-stack Azure activity log Jan 27 01:12:35.004: INFO: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-kxootk-dual-stack-control-plane-c89x7, container kube-scheduler Jan 27 01:12:35.004: INFO: Describing Pod kube-system/kube-scheduler-capz-e2e-kxootk-dual-stack-control-plane-c89x7 Jan 27 01:12:40.326: INFO: Fetching activity logs took 5.322117973s Jan 27 01:12:40.326: INFO: Dumping all the Cluster API resources in the "capz-e2e-kxootk" namespace Jan 27 01:12:40.652: INFO: Deleting all clusters in the capz-e2e-kxootk namespace STEP: Deleting cluster capz-e2e-kxootk-dual-stack - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:12:40.67 INFO: Waiting for the Cluster capz-e2e-kxootk/capz-e2e-kxootk-dual-stack to be deleted STEP: Waiting for cluster capz-e2e-kxootk-dual-stack to be deleted - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:12:40.684 Jan 27 01:16:21.032: INFO: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace capz-e2e-kxootk Jan 27 01:16:21.050: INFO: Checking if any resources are left over in Azure for spec "create-workload-cluster" STEP: Redacting sensitive information from logs - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:216 @ 01/27/23 01:16:21.722 INFO: "With dual-stack worker node" started at Fri, 27 Jan 2023 01:17:37 UTC on Ginkgo node 10 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml < Exit [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:17:37.789 (5m19.908s)
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sWorkload\scluster\screation\sCreating\sa\sprivate\scluster\s\[OPTIONAL\]\sCreates\sa\spublic\smanagement\scluster\sin\sa\scustom\svnet$'
[FAILED] Timed out after 1200.001s. No Control Plane machines came into existence. Expected <bool>: false to be true In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:03:21.682from junit.e2e_suite.1.xml
2023/01/27 00:38:58 failed trying to get namespace (capz-e2e-4fcvyp):namespaces "capz-e2e-4fcvyp" not found cluster.cluster.x-k8s.io/capz-e2e-4fcvyp-public-custom-vnet created azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-4fcvyp-public-custom-vnet created kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-4fcvyp-public-custom-vnet-control-plane created azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-4fcvyp-public-custom-vnet-control-plane created machinedeployment.cluster.x-k8s.io/capz-e2e-4fcvyp-public-custom-vnet-md-0 created azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-4fcvyp-public-custom-vnet-md-0 created kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-4fcvyp-public-custom-vnet-md-0 created azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created machinehealthcheck.cluster.x-k8s.io/capz-e2e-4fcvyp-public-custom-vnet-mhc-0 created felixconfiguration.crd.projectcalico.org/default configured Failed to get logs for Machine capz-e2e-4fcvyp-public-custom-vnet-md-0-56859b55bb-cc9j7, Cluster capz-e2e-4fcvyp/capz-e2e-4fcvyp-public-custom-vnet: [dialing from control plane to target node at capz-e2e-4fcvyp-public-custom-vnet-md-0-7wr7k: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: failed to get boot diagnostics data: compute.VirtualMachinesClient#RetrieveBootDiagnosticsData: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="The Resource 'Microsoft.Compute/virtualMachines/capz-e2e-4fcvyp-public-custom-vnet-md-0-7wr7k' under resource group 'capz-e2e-4fcvyp-public-custom-vnet' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix"] > Enter [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.355 INFO: "" started at Fri, 27 Jan 2023 00:38:58 UTC on Ginkgo node 1 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml STEP: Creating namespace "capz-e2e-4fcvyp" for hosting the cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:38:58.355 Jan 27 00:38:58.355: INFO: starting to create namespace for hosting the "capz-e2e-4fcvyp" test spec INFO: Creating namespace capz-e2e-4fcvyp INFO: Creating event watcher for namespace "capz-e2e-4fcvyp" Jan 27 00:38:58.425: INFO: Creating cluster identity secret "cluster-identity-secret" < Exit [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.522 (168ms) > Enter [It] Creates a public management cluster in a custom vnet - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:156 @ 01/27/23 00:38:58.522 INFO: Cluster name is capz-e2e-4fcvyp-public-custom-vnet STEP: Creating a custom virtual network - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:158 @ 01/27/23 00:38:58.522 STEP: creating Azure clients with the workload cluster's subscription - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_privatecluster.go:223 @ 01/27/23 00:38:58.522 STEP: creating a resource group - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_privatecluster.go:238 @ 01/27/23 00:38:58.523 STEP: creating a network security group - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_privatecluster.go:249 @ 01/27/23 00:39:01.334 STEP: creating a node security group - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_privatecluster.go:291 @ 01/27/23 00:39:05.437 STEP: creating a node routetable - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_privatecluster.go:304 @ 01/27/23 00:39:09.293 STEP: creating a virtual network - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_privatecluster.go:315 @ 01/27/23 00:39:12.196 END STEP: Creating a custom virtual network - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:158 @ 01/27/23 00:39:16.19 (17.667s) INFO: Creating the workload cluster with name "capz-e2e-4fcvyp-public-custom-vnet" using the "custom-vnet" template (Kubernetes v1.24.10, 1 control-plane machines, 1 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-e2e-4fcvyp-public-custom-vnet --infrastructure (default) --kubernetes-version v1.24.10 --control-plane-machine-count 1 --worker-machine-count 1 --flavor custom-vnet INFO: Applying the cluster template yaml to the cluster INFO: Waiting for the cluster infrastructure to be provisioned STEP: Waiting for cluster to enter the provisioned phase - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/cluster_helpers.go:134 @ 01/27/23 00:39:16.871 INFO: Waiting for control plane to be initialized STEP: Installing cloud-provider-azure components via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:45 @ 01/27/23 00:39:46.91 Jan 27 00:41:50.086: INFO: getting history for release cloud-provider-azure-oot Jan 27 00:41:50.117: INFO: Release cloud-provider-azure-oot does not exist, installing it Jan 27 00:41:51.497: INFO: creating 1 resource(s) Jan 27 00:41:51.574: INFO: creating 10 resource(s) Jan 27 00:41:51.829: INFO: Install complete STEP: Installing Calico CNI via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:51 @ 01/27/23 00:41:51.829 STEP: Configuring calico CNI helm chart for IPv4 configuration - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:112 @ 01/27/23 00:41:51.829 Jan 27 00:41:51.878: INFO: getting history for release projectcalico Jan 27 00:41:51.907: INFO: Release projectcalico does not exist, installing it Jan 27 00:41:52.519: INFO: creating 1 resource(s) Jan 27 00:41:52.562: INFO: creating 1 resource(s) Jan 27 00:41:52.610: INFO: creating 1 resource(s) Jan 27 00:41:52.650: INFO: creating 1 resource(s) Jan 27 00:41:52.700: INFO: creating 1 resource(s) Jan 27 00:41:52.746: INFO: creating 1 resource(s) Jan 27 00:41:52.841: INFO: creating 1 resource(s) Jan 27 00:41:52.913: INFO: creating 1 resource(s) Jan 27 00:41:52.950: INFO: creating 1 resource(s) Jan 27 00:41:52.992: INFO: creating 1 resource(s) Jan 27 00:41:53.033: INFO: creating 1 resource(s) Jan 27 00:41:53.100: INFO: creating 1 resource(s) Jan 27 00:41:53.169: INFO: creating 1 resource(s) Jan 27 00:41:53.233: INFO: creating 1 resource(s) Jan 27 00:41:53.272: INFO: creating 1 resource(s) Jan 27 00:41:53.317: INFO: creating 1 resource(s) Jan 27 00:41:53.369: INFO: creating 1 resource(s) Jan 27 00:41:53.417: INFO: creating 1 resource(s) Jan 27 00:41:53.476: INFO: creating 1 resource(s) Jan 27 00:41:53.581: INFO: creating 1 resource(s) Jan 27 00:41:53.828: INFO: creating 1 resource(s) Jan 27 00:41:53.864: INFO: Clearing discovery cache Jan 27 00:41:53.864: INFO: beginning wait for 21 resources with timeout of 1m0s Jan 27 00:41:56.158: INFO: creating 1 resource(s) Jan 27 00:41:56.505: INFO: creating 6 resource(s) Jan 27 00:41:57.002: INFO: Install complete STEP: Waiting for Ready tigera-operator deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:60 @ 01/27/23 00:41:57.235 STEP: waiting for deployment tigera-operator/tigera-operator to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:41:57.353 Jan 27 00:41:57.353: INFO: starting to wait for deployment to become available Jan 27 00:42:08.692: INFO: Deployment tigera-operator/tigera-operator is now available, took 11.338949787s STEP: Waiting for Ready calico-system deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:74 @ 01/27/23 00:42:09.187 STEP: waiting for deployment calico-system/calico-kube-controllers to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:42:09.331 Jan 27 00:42:09.331: INFO: starting to wait for deployment to become available Jan 27 00:42:59.992: INFO: Deployment calico-system/calico-kube-controllers is now available, took 50.66070707s STEP: waiting for deployment calico-system/calico-typha to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:43:00.238 Jan 27 00:43:00.238: INFO: starting to wait for deployment to become available Jan 27 00:43:00.266: INFO: Deployment calico-system/calico-typha is now available, took 27.604327ms STEP: Waiting for Ready calico-apiserver deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:79 @ 01/27/23 00:43:00.266 STEP: waiting for deployment calico-apiserver/calico-apiserver to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:43:00.632 Jan 27 00:43:00.632: INFO: starting to wait for deployment to become available Jan 27 00:43:21.458: INFO: Deployment calico-apiserver/calico-apiserver is now available, took 20.825659792s STEP: Waiting for Ready cloud-controller-manager deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:55 @ 01/27/23 00:43:21.486 STEP: waiting for deployment kube-system/cloud-controller-manager to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:43:21.629 Jan 27 00:43:21.629: INFO: starting to wait for deployment to become available Jan 27 00:43:21.656: INFO: Deployment kube-system/cloud-controller-manager is now available, took 27.563252ms INFO: Waiting for the first control plane machine managed by capz-e2e-4fcvyp/capz-e2e-4fcvyp-public-custom-vnet-control-plane to be provisioned STEP: Waiting for one control plane node to exist - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:133 @ 01/27/23 00:43:21.68 [FAILED] Timed out after 1200.001s. No Control Plane machines came into existence. Expected <bool>: false to be true In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:03:21.682 < Exit [It] Creates a public management cluster in a custom vnet - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:156 @ 01/27/23 01:03:21.682 (24m23.16s) > Enter [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:03:21.682 Jan 27 01:03:21.682: INFO: FAILED! Jan 27 01:03:21.682: INFO: Cleaning up after "Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet" spec STEP: Dumping logs from the "capz-e2e-4fcvyp-public-custom-vnet" workload cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 01:03:21.682 Jan 27 01:03:21.682: INFO: Dumping workload cluster capz-e2e-4fcvyp/capz-e2e-4fcvyp-public-custom-vnet logs Jan 27 01:03:21.726: INFO: Collecting logs for Linux node capz-e2e-4fcvyp-public-custom-vnet-control-plane-vlv57 in cluster capz-e2e-4fcvyp-public-custom-vnet in namespace capz-e2e-4fcvyp Jan 27 01:03:32.668: INFO: Collecting boot logs for AzureMachine capz-e2e-4fcvyp-public-custom-vnet-control-plane-vlv57 Jan 27 01:03:33.597: INFO: Collecting logs for Linux node capz-e2e-4fcvyp-public-custom-vnet-md-0-7wr7k in cluster capz-e2e-4fcvyp-public-custom-vnet in namespace capz-e2e-4fcvyp Jan 27 01:04:38.661: INFO: Collecting boot logs for AzureMachine capz-e2e-4fcvyp-public-custom-vnet-md-0-7wr7k Jan 27 01:04:38.985: INFO: Dumping workload cluster capz-e2e-4fcvyp/capz-e2e-4fcvyp-public-custom-vnet kube-system pod logs Jan 27 01:04:39.416: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-5d5c7b8545-2m2sl, container calico-apiserver Jan 27 01:04:39.416: INFO: Describing Pod calico-apiserver/calico-apiserver-5d5c7b8545-2m2sl Jan 27 01:04:39.487: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-5d5c7b8545-vwcj5, container calico-apiserver Jan 27 01:04:39.487: INFO: Describing Pod calico-apiserver/calico-apiserver-5d5c7b8545-vwcj5 Jan 27 01:04:39.554: INFO: Creating log watcher for controller calico-system/calico-kube-controllers-594d54f99-rtgjm, container calico-kube-controllers Jan 27 01:04:39.554: INFO: Describing Pod calico-system/calico-kube-controllers-594d54f99-rtgjm Jan 27 01:04:39.625: INFO: Creating log watcher for controller calico-system/calico-node-2z9w4, container calico-node Jan 27 01:04:39.625: INFO: Describing Pod calico-system/calico-node-2z9w4 Jan 27 01:04:39.701: INFO: Creating log watcher for controller calico-system/calico-typha-74c89cd8bd-vvk69, container calico-typha Jan 27 01:04:39.701: INFO: Describing Pod calico-system/calico-typha-74c89cd8bd-vvk69 Jan 27 01:04:39.780: INFO: Describing Pod calico-system/csi-node-driver-gqxgm Jan 27 01:04:39.780: INFO: Creating log watcher for controller calico-system/csi-node-driver-gqxgm, container calico-csi Jan 27 01:04:39.780: INFO: Creating log watcher for controller calico-system/csi-node-driver-gqxgm, container csi-node-driver-registrar Jan 27 01:04:40.185: INFO: Describing Pod kube-system/cloud-controller-manager-5dd6565c55-hv5t4 Jan 27 01:04:40.185: INFO: Creating log watcher for controller kube-system/cloud-controller-manager-5dd6565c55-hv5t4, container cloud-controller-manager Jan 27 01:04:40.580: INFO: Describing Pod kube-system/cloud-node-manager-trzdq Jan 27 01:04:40.580: INFO: Creating log watcher for controller kube-system/cloud-node-manager-trzdq, container cloud-node-manager Jan 27 01:04:40.980: INFO: Describing Pod kube-system/coredns-57575c5f89-7vxvh Jan 27 01:04:40.980: INFO: Creating log watcher for controller kube-system/coredns-57575c5f89-7vxvh, container coredns Jan 27 01:04:41.379: INFO: Describing Pod kube-system/coredns-57575c5f89-t6wtv Jan 27 01:04:41.379: INFO: Creating log watcher for controller kube-system/coredns-57575c5f89-t6wtv, container coredns Jan 27 01:04:41.780: INFO: Creating log watcher for controller kube-system/etcd-capz-e2e-4fcvyp-public-custom-vnet-control-plane-vlv57, container etcd Jan 27 01:04:41.780: INFO: Describing Pod kube-system/etcd-capz-e2e-4fcvyp-public-custom-vnet-control-plane-vlv57 Jan 27 01:04:42.183: INFO: Describing Pod kube-system/kube-apiserver-capz-e2e-4fcvyp-public-custom-vnet-control-plane-vlv57 Jan 27 01:04:42.183: INFO: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-4fcvyp-public-custom-vnet-control-plane-vlv57, container kube-apiserver Jan 27 01:04:42.580: INFO: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-4fcvyp-public-custom-vnet-control-plane-vlv57, container kube-controller-manager Jan 27 01:04:42.580: INFO: Describing Pod kube-system/kube-controller-manager-capz-e2e-4fcvyp-public-custom-vnet-control-plane-vlv57 Jan 27 01:04:42.979: INFO: Describing Pod kube-system/kube-proxy-pvbsk Jan 27 01:04:42.979: INFO: Creating log watcher for controller kube-system/kube-proxy-pvbsk, container kube-proxy Jan 27 01:04:43.380: INFO: Describing Pod kube-system/kube-scheduler-capz-e2e-4fcvyp-public-custom-vnet-control-plane-vlv57 Jan 27 01:04:43.380: INFO: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-4fcvyp-public-custom-vnet-control-plane-vlv57, container kube-scheduler Jan 27 01:04:43.779: INFO: Fetching kube-system pod logs took 4.794317096s Jan 27 01:04:43.779: INFO: Dumping workload cluster capz-e2e-4fcvyp/capz-e2e-4fcvyp-public-custom-vnet Azure activity log Jan 27 01:04:43.779: INFO: Creating log watcher for controller tigera-operator/tigera-operator-65d6bf4d4f-xw5g6, container tigera-operator Jan 27 01:04:43.779: INFO: Describing Pod tigera-operator/tigera-operator-65d6bf4d4f-xw5g6 Jan 27 01:04:47.476: INFO: Fetching activity logs took 3.697321194s Jan 27 01:04:47.476: INFO: Dumping all the Cluster API resources in the "capz-e2e-4fcvyp" namespace Jan 27 01:04:47.838: INFO: Deleting all clusters in the capz-e2e-4fcvyp namespace STEP: Deleting cluster capz-e2e-4fcvyp-public-custom-vnet - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:04:47.86 INFO: Waiting for the Cluster capz-e2e-4fcvyp/capz-e2e-4fcvyp-public-custom-vnet to be deleted STEP: Waiting for cluster capz-e2e-4fcvyp-public-custom-vnet to be deleted - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:04:47.872 Jan 27 01:07:47.968: INFO: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace capz-e2e-4fcvyp Jan 27 01:07:47.989: INFO: Running additional cleanup for the "create-workload-cluster" test spec Jan 27 01:07:47.989: INFO: deleting an existing virtual network "custom-vnet" Jan 27 01:07:58.512: INFO: deleting an existing route table "node-routetable" Jan 27 01:08:00.901: INFO: deleting an existing network security group "node-nsg" Jan 27 01:08:11.220: INFO: deleting an existing network security group "control-plane-nsg" Jan 27 01:08:21.626: INFO: verifying the existing resource group "capz-e2e-4fcvyp-public-custom-vnet" is empty Jan 27 01:08:21.699: INFO: deleting the existing resource group "capz-e2e-4fcvyp-public-custom-vnet" Jan 27 01:09:37.991: INFO: Checking if any resources are left over in Azure for spec "create-workload-cluster" STEP: Redacting sensitive information from logs - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:216 @ 01/27/23 01:09:38.369 INFO: "Creates a public management cluster in a custom vnet" started at Fri, 27 Jan 2023 01:11:04 UTC on Ginkgo node 1 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml < Exit [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:11:04.862 (7m43.18s)
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sWorkload\scluster\screation\sCreating\sclusters\susing\sclusterclass\s\[OPTIONAL\]\swith\sa\ssingle\scontrol\splane\snode\,\sone\slinux\sworker\snode\,\sand\sone\swindows\sworker\snode$'
[FAILED] Timed out after 1200.000s. No Control Plane machines came into existence. Expected <bool>: false to be true In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:05:18.983from junit.e2e_suite.1.xml
2023/01/27 00:38:58 failed trying to get namespace (capz-e2e-mkpbrv):namespaces "capz-e2e-mkpbrv" not found clusterclass.cluster.x-k8s.io/ci-default created kubeadmcontrolplanetemplate.controlplane.cluster.x-k8s.io/ci-default-kubeadm-control-plane created azureclustertemplate.infrastructure.cluster.x-k8s.io/ci-default-azure-cluster created azuremachinetemplate.infrastructure.cluster.x-k8s.io/ci-default-control-plane created kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/ci-default-worker created azuremachinetemplate.infrastructure.cluster.x-k8s.io/ci-default-worker created kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/ci-default-worker-win created azuremachinetemplate.infrastructure.cluster.x-k8s.io/ci-default-worker-win created azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created cluster.cluster.x-k8s.io/capz-e2e-mkpbrv-cc created clusterresourceset.addons.cluster.x-k8s.io/capz-e2e-mkpbrv-cc-calico created clusterresourceset.addons.cluster.x-k8s.io/csi-proxy created configmap/cni-capz-e2e-mkpbrv-cc-calico-windows created configmap/csi-proxy-addon created felixconfiguration.crd.projectcalico.org/default configured Failed to get logs for Machine capz-e2e-mkpbrv-cc-cv2vj-dvvz2, Cluster capz-e2e-mkpbrv/capz-e2e-mkpbrv-cc: dialing public load balancer at capz-e2e-mkpbrv-cc-6d2ce877.eastus.cloudapp.azure.com: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain Failed to get logs for Machine capz-e2e-mkpbrv-cc-md-0-69d2w-676664c57f-cwtdl, Cluster capz-e2e-mkpbrv/capz-e2e-mkpbrv-cc: azuremachines.infrastructure.cluster.x-k8s.io "capz-e2e-mkpbrv-cc-md-0-infra-rzrjz-s9vhr" not found Failed to get logs for Machine capz-e2e-mkpbrv-cc-md-win-4ntpb-6568b6f7cd-fm896, Cluster capz-e2e-mkpbrv/capz-e2e-mkpbrv-cc: azuremachines.infrastructure.cluster.x-k8s.io "capz-e2e-mkpbrv-cc-md-win-infra-ppfkt-rhhw9" not found > Enter [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.406 INFO: "" started at Fri, 27 Jan 2023 00:38:58 UTC on Ginkgo node 4 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml STEP: Creating namespace "capz-e2e-mkpbrv" for hosting the cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:38:58.406 Jan 27 00:38:58.406: INFO: starting to create namespace for hosting the "capz-e2e-mkpbrv" test spec INFO: Creating namespace capz-e2e-mkpbrv INFO: Creating event watcher for namespace "capz-e2e-mkpbrv" Jan 27 00:38:58.565: INFO: Using existing cluster identity secret < Exit [BeforeEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:56 @ 01/27/23 00:38:58.565 (159ms) > Enter [It] with a single control plane node, one linux worker node, and one windows worker node - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:904 @ 01/27/23 00:38:58.565 INFO: Cluster name is capz-e2e-mkpbrv-cc INFO: Creating the workload cluster with name "capz-e2e-mkpbrv-cc" using the "topology" template (Kubernetes v1.24.10, 1 control-plane machines, 1 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-e2e-mkpbrv-cc --infrastructure (default) --kubernetes-version v1.24.10 --control-plane-machine-count 1 --worker-machine-count 1 --flavor topology INFO: Applying the cluster template yaml to the cluster INFO: Waiting for the cluster infrastructure to be provisioned STEP: Waiting for cluster to enter the provisioned phase - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/cluster_helpers.go:134 @ 01/27/23 00:39:04.608 INFO: Waiting for control plane to be initialized STEP: Installing cloud-provider-azure components via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:45 @ 01/27/23 00:40:54.728 Jan 27 00:42:57.991: INFO: getting history for release cloud-provider-azure-oot Jan 27 00:42:58.023: INFO: Release cloud-provider-azure-oot does not exist, installing it Jan 27 00:42:59.533: INFO: creating 1 resource(s) Jan 27 00:42:59.637: INFO: creating 10 resource(s) Jan 27 00:42:59.950: INFO: Install complete STEP: Installing Calico CNI via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:51 @ 01/27/23 00:42:59.95 STEP: Configuring calico CNI helm chart for IPv4 configuration - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:112 @ 01/27/23 00:42:59.95 Jan 27 00:43:00.004: INFO: getting history for release projectcalico Jan 27 00:43:00.043: INFO: Release projectcalico does not exist, installing it Jan 27 00:43:00.595: INFO: creating 1 resource(s) Jan 27 00:43:00.650: INFO: creating 1 resource(s) Jan 27 00:43:00.693: INFO: creating 1 resource(s) Jan 27 00:43:00.740: INFO: creating 1 resource(s) Jan 27 00:43:00.790: INFO: creating 1 resource(s) Jan 27 00:43:00.837: INFO: creating 1 resource(s) Jan 27 00:43:00.947: INFO: creating 1 resource(s) Jan 27 00:43:01.014: INFO: creating 1 resource(s) Jan 27 00:43:01.086: INFO: creating 1 resource(s) Jan 27 00:43:01.159: INFO: creating 1 resource(s) Jan 27 00:43:01.206: INFO: creating 1 resource(s) Jan 27 00:43:01.247: INFO: creating 1 resource(s) Jan 27 00:43:01.293: INFO: creating 1 resource(s) Jan 27 00:43:01.340: INFO: creating 1 resource(s) Jan 27 00:43:01.396: INFO: creating 1 resource(s) Jan 27 00:43:01.529: INFO: creating 1 resource(s) Jan 27 00:43:01.602: INFO: creating 1 resource(s) Jan 27 00:43:01.668: INFO: creating 1 resource(s) Jan 27 00:43:01.732: INFO: creating 1 resource(s) Jan 27 00:43:01.835: INFO: creating 1 resource(s) Jan 27 00:43:02.064: INFO: creating 1 resource(s) Jan 27 00:43:02.148: INFO: Clearing discovery cache Jan 27 00:43:02.148: INFO: beginning wait for 21 resources with timeout of 1m0s Jan 27 00:43:05.036: INFO: creating 1 resource(s) Jan 27 00:43:05.404: INFO: creating 6 resource(s) Jan 27 00:43:05.962: INFO: Install complete STEP: Waiting for Ready tigera-operator deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:60 @ 01/27/23 00:43:06.254 STEP: waiting for deployment tigera-operator/tigera-operator to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:43:06.393 Jan 27 00:43:06.393: INFO: starting to wait for deployment to become available Jan 27 00:43:16.457: INFO: Deployment tigera-operator/tigera-operator is now available, took 10.064429686s STEP: Waiting for Ready calico-system deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:74 @ 01/27/23 00:43:17.699 STEP: waiting for deployment calico-system/calico-kube-controllers to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:43:17.857 Jan 27 00:43:17.857: INFO: starting to wait for deployment to become available Jan 27 00:44:08.133: INFO: Deployment calico-system/calico-kube-controllers is now available, took 50.27534874s STEP: waiting for deployment calico-system/calico-typha to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:44:08.295 Jan 27 00:44:08.295: INFO: starting to wait for deployment to become available Jan 27 00:44:08.327: INFO: Deployment calico-system/calico-typha is now available, took 31.83023ms STEP: Waiting for Ready calico-apiserver deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:79 @ 01/27/23 00:44:08.327 STEP: waiting for deployment calico-apiserver/calico-apiserver to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:44:18.52 Jan 27 00:44:18.520: INFO: starting to wait for deployment to become available Jan 27 00:45:18.751: INFO: Deployment calico-apiserver/calico-apiserver is now available, took 1m0.230985476s STEP: Waiting for Ready cloud-controller-manager deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:55 @ 01/27/23 00:45:18.768 STEP: waiting for deployment kube-system/cloud-controller-manager to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 00:45:18.93 Jan 27 00:45:18.930: INFO: starting to wait for deployment to become available Jan 27 00:45:18.962: INFO: Deployment kube-system/cloud-controller-manager is now available, took 32.24731ms INFO: Waiting for the first control plane machine managed by capz-e2e-mkpbrv/capz-e2e-mkpbrv-cc-cv2vj to be provisioned STEP: Waiting for one control plane node to exist - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:133 @ 01/27/23 00:45:18.982 [FAILED] Timed out after 1200.000s. No Control Plane machines came into existence. Expected <bool>: false to be true In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/controlplane_helpers.go:154 @ 01/27/23 01:05:18.983 < Exit [It] with a single control plane node, one linux worker node, and one windows worker node - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:904 @ 01/27/23 01:05:18.983 (26m20.418s) > Enter [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:05:18.983 Jan 27 01:05:18.983: INFO: FAILED! Jan 27 01:05:18.983: INFO: Cleaning up after "Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node" spec STEP: Dumping logs from the "capz-e2e-mkpbrv-cc" workload cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/27/23 01:05:18.983 Jan 27 01:05:18.983: INFO: Dumping workload cluster capz-e2e-mkpbrv/capz-e2e-mkpbrv-cc logs Jan 27 01:05:19.028: INFO: Collecting logs for Linux node capz-e2e-mkpbrv-cc-control-plane-t7l8w-58qtt in cluster capz-e2e-mkpbrv-cc in namespace capz-e2e-mkpbrv Jan 27 01:06:19.943: INFO: Collecting boot logs for AzureMachine capz-e2e-mkpbrv-cc-control-plane-t7l8w-58qtt Jan 27 01:06:20.959: INFO: Dumping workload cluster capz-e2e-mkpbrv/capz-e2e-mkpbrv-cc kube-system pod logs Jan 27 01:06:21.323: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-84d9b48fc7-lkvcv, container calico-apiserver Jan 27 01:06:21.323: INFO: Describing Pod calico-apiserver/calico-apiserver-84d9b48fc7-lkvcv Jan 27 01:06:21.380: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-84d9b48fc7-zh9sz, container calico-apiserver Jan 27 01:06:21.382: INFO: Describing Pod calico-apiserver/calico-apiserver-84d9b48fc7-zh9sz Jan 27 01:06:21.439: INFO: Describing Pod calico-system/calico-kube-controllers-594d54f99-fckxw Jan 27 01:06:21.439: INFO: Creating log watcher for controller calico-system/calico-kube-controllers-594d54f99-fckxw, container calico-kube-controllers Jan 27 01:06:21.501: INFO: Creating log watcher for controller calico-system/calico-node-l8r9m, container calico-node Jan 27 01:06:21.501: INFO: Describing Pod calico-system/calico-node-l8r9m Jan 27 01:06:21.587: INFO: Creating log watcher for controller calico-system/calico-node-nn7kv, container calico-node Jan 27 01:06:21.587: INFO: Describing Pod calico-system/calico-node-nn7kv Jan 27 01:06:21.619: INFO: Error starting logs stream for pod calico-system/calico-node-nn7kv, container calico-node: Get "https://10.1.0.5:10250/containerLogs/calico-system/calico-node-nn7kv/calico-node?follow=true": dial tcp 10.1.0.5:10250: connect: connection refused Jan 27 01:06:21.689: INFO: Describing Pod calico-system/calico-typha-69df76cbfb-226bl Jan 27 01:06:21.689: INFO: Creating log watcher for controller calico-system/calico-typha-69df76cbfb-226bl, container calico-typha Jan 27 01:06:22.088: INFO: Creating log watcher for controller calico-system/calico-typha-69df76cbfb-7v4zp, container calico-typha Jan 27 01:06:22.088: INFO: Describing Pod calico-system/calico-typha-69df76cbfb-7v4zp Jan 27 01:06:22.119: INFO: Error starting logs stream for pod calico-system/calico-typha-69df76cbfb-7v4zp, container calico-typha: Get "https://10.1.0.5:10250/containerLogs/calico-system/calico-typha-69df76cbfb-7v4zp/calico-typha?follow=true": dial tcp 10.1.0.5:10250: connect: connection refused Jan 27 01:06:22.490: INFO: Creating log watcher for controller calico-system/csi-node-driver-cpt2k, container calico-csi Jan 27 01:06:22.490: INFO: Creating log watcher for controller calico-system/csi-node-driver-cpt2k, container csi-node-driver-registrar Jan 27 01:06:22.490: INFO: Describing Pod calico-system/csi-node-driver-cpt2k Jan 27 01:06:22.889: INFO: Describing Pod calico-system/csi-node-driver-rd92q Jan 27 01:06:22.890: INFO: Creating log watcher for controller calico-system/csi-node-driver-rd92q, container calico-csi Jan 27 01:06:22.891: INFO: Creating log watcher for controller calico-system/csi-node-driver-rd92q, container csi-node-driver-registrar Jan 27 01:06:22.920: INFO: Error starting logs stream for pod calico-system/csi-node-driver-rd92q, container calico-csi: Get "https://10.1.0.5:10250/containerLogs/calico-system/csi-node-driver-rd92q/calico-csi?follow=true": dial tcp 10.1.0.5:10250: connect: connection refused Jan 27 01:06:22.922: INFO: Error starting logs stream for pod calico-system/csi-node-driver-rd92q, container csi-node-driver-registrar: Get "https://10.1.0.5:10250/containerLogs/calico-system/csi-node-driver-rd92q/csi-node-driver-registrar?follow=true": dial tcp 10.1.0.5:10250: connect: connection refused Jan 27 01:06:23.289: INFO: Creating log watcher for controller kube-system/cloud-controller-manager-8ff498b98-969dh, container cloud-controller-manager Jan 27 01:06:23.289: INFO: Describing Pod kube-system/cloud-controller-manager-8ff498b98-969dh Jan 27 01:06:23.689: INFO: Creating log watcher for controller kube-system/cloud-node-manager-7rs5r, container cloud-node-manager Jan 27 01:06:23.689: INFO: Describing Pod kube-system/cloud-node-manager-7rs5r Jan 27 01:06:24.090: INFO: Creating log watcher for controller kube-system/cloud-node-manager-z4dxc, container cloud-node-manager Jan 27 01:06:24.090: INFO: Describing Pod kube-system/cloud-node-manager-z4dxc Jan 27 01:06:24.121: INFO: Error starting logs stream for pod kube-system/cloud-node-manager-z4dxc, container cloud-node-manager: Get "https://10.1.0.5:10250/containerLogs/kube-system/cloud-node-manager-z4dxc/cloud-node-manager?follow=true": dial tcp 10.1.0.5:10250: connect: connection refused Jan 27 01:06:24.490: INFO: Describing Pod kube-system/coredns-57575c5f89-52gfh Jan 27 01:06:24.490: INFO: Creating log watcher for controller kube-system/coredns-57575c5f89-52gfh, container coredns Jan 27 01:06:24.889: INFO: Describing Pod kube-system/coredns-57575c5f89-v7rhj Jan 27 01:06:24.889: INFO: Creating log watcher for controller kube-system/coredns-57575c5f89-v7rhj, container coredns Jan 27 01:06:25.288: INFO: Describing Pod kube-system/etcd-capz-e2e-mkpbrv-cc-control-plane-t7l8w-58qtt Jan 27 01:06:25.288: INFO: Creating log watcher for controller kube-system/etcd-capz-e2e-mkpbrv-cc-control-plane-t7l8w-58qtt, container etcd Jan 27 01:06:25.689: INFO: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-mkpbrv-cc-control-plane-t7l8w-58qtt, container kube-apiserver Jan 27 01:06:25.689: INFO: Describing Pod kube-system/kube-apiserver-capz-e2e-mkpbrv-cc-control-plane-t7l8w-58qtt Jan 27 01:06:26.089: INFO: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-mkpbrv-cc-control-plane-t7l8w-58qtt, container kube-controller-manager Jan 27 01:06:26.089: INFO: Describing Pod kube-system/kube-controller-manager-capz-e2e-mkpbrv-cc-control-plane-t7l8w-58qtt Jan 27 01:06:26.489: INFO: Creating log watcher for controller kube-system/kube-proxy-d4w7l, container kube-proxy Jan 27 01:06:26.489: INFO: Describing Pod kube-system/kube-proxy-d4w7l Jan 27 01:06:26.520: INFO: Error starting logs stream for pod kube-system/kube-proxy-d4w7l, container kube-proxy: Get "https://10.1.0.5:10250/containerLogs/kube-system/kube-proxy-d4w7l/kube-proxy?follow=true": dial tcp 10.1.0.5:10250: connect: connection refused Jan 27 01:06:26.898: INFO: Describing Pod kube-system/kube-proxy-dxqrr Jan 27 01:06:26.898: INFO: Creating log watcher for controller kube-system/kube-proxy-dxqrr, container kube-proxy Jan 27 01:06:27.289: INFO: Describing Pod kube-system/kube-scheduler-capz-e2e-mkpbrv-cc-control-plane-t7l8w-58qtt Jan 27 01:06:27.289: INFO: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-mkpbrv-cc-control-plane-t7l8w-58qtt, container kube-scheduler Jan 27 01:06:27.687: INFO: Fetching kube-system pod logs took 6.727305291s Jan 27 01:06:27.687: INFO: Dumping workload cluster capz-e2e-mkpbrv/capz-e2e-mkpbrv-cc Azure activity log Jan 27 01:06:27.687: INFO: Creating log watcher for controller tigera-operator/tigera-operator-65d6bf4d4f-rhp4x, container tigera-operator Jan 27 01:06:27.687: INFO: Describing Pod tigera-operator/tigera-operator-65d6bf4d4f-rhp4x Jan 27 01:06:27.708: INFO: Error fetching activity logs for cluster capz-e2e-mkpbrv-cc in namespace capz-e2e-mkpbrv. Not able to find the AzureManagedControlPlane on the management cluster: azuremanagedcontrolplanes.infrastructure.cluster.x-k8s.io "capz-e2e-mkpbrv-cc" not found Jan 27 01:06:27.708: INFO: Fetching activity logs took 21.380521ms Jan 27 01:06:27.708: INFO: Dumping all the Cluster API resources in the "capz-e2e-mkpbrv" namespace Jan 27 01:06:28.246: INFO: Deleting all clusters in the capz-e2e-mkpbrv namespace STEP: Deleting cluster capz-e2e-mkpbrv-cc - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:06:28.273 INFO: Waiting for the Cluster capz-e2e-mkpbrv/capz-e2e-mkpbrv-cc to be deleted STEP: Waiting for cluster capz-e2e-mkpbrv-cc to be deleted - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/27/23 01:06:28.284 Jan 27 01:11:08.550: INFO: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace capz-e2e-mkpbrv Jan 27 01:11:08.583: INFO: Checking if any resources are left over in Azure for spec "create-workload-cluster" STEP: Redacting sensitive information from logs - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:216 @ 01/27/23 01:11:09.172 INFO: "with a single control plane node, one linux worker node, and one windows worker node" started at Fri, 27 Jan 2023 01:12:35 UTC on Ginkgo node 4 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml < Exit [AfterEach] Workload cluster creation - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:117 @ 01/27/23 01:12:35.467 (7m16.484s)
Filter through log files | View test history on testgrid
capz-e2e [It] Workload cluster creation Creating a cluster that uses the intree cloud provider [OPTIONAL] with a 1 control plane nodes and 2 worker nodes
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [It] Conformance Tests conformance-tests
capz-e2e [It] Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 Should create a management cluster and then upgrade all the providers
capz-e2e [It] Running the Cluster API E2E tests Running KCP upgrade in a HA cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Running KCP upgrade in a HA cluster using scale in rollout [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e [It] Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e [It] Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e [It] Running the Cluster API E2E tests Running the workload cluster upgrade spec [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e [It] Running the Cluster API E2E tests Should successfully scale out and scale in a MachineDeployment Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capz-e2e [It] Running the Cluster API E2E tests Should successfully set and use node drain timeout A node should be forcefully removed if it cannot be drained in time
capz-e2e [It] Workload cluster creation Creating a VMSS cluster [REQUIRED] with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes
capz-e2e [It] Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e [It] Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e [It] Workload cluster creation Creating an AKS cluster [Managed Kubernetes] with a single control plane node and 1 node