Recent runs || View in Spyglass
Result | FAILURE |
Tests | 2 failed / 7 succeeded |
Started | |
Elapsed | 1h36m |
Revision | release-0.5 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sWorkload\scluster\screation\sCreating\sa\sWindows\senabled\sVMSS\scluster\swith\sa\ssingle\scontrol\splane\snode\sand\san\sLinux\sAzureMachinePool\swith\s1\snodes\sand\sWindows\sAzureMachinePool\swith\s1\snode$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:543 Timed out after 900.000s. Expected <int>: 0 to equal <int>: 1 /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v0.4.8-0.20220215165403-0234afe87ffe/framework/machinepool_helpers.go:85from junit.e2e_suite.3.xml
INFO: "with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node" started at Fri, 15 Apr 2022 20:33:42 UTC on Ginkgo node 3 of 3 �[1mSTEP�[0m: Creating namespace "capz-e2e-ibeva2" for hosting the cluster Apr 15 20:33:42.699: INFO: starting to create namespace for hosting the "capz-e2e-ibeva2" test spec 2022/04/15 20:33:42 failed trying to get namespace (capz-e2e-ibeva2):namespaces "capz-e2e-ibeva2" not found INFO: Creating namespace capz-e2e-ibeva2 INFO: Creating event watcher for namespace "capz-e2e-ibeva2" Apr 15 20:33:42.745: INFO: Creating cluster identity secret %!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-ibeva2-win-vmss INFO: Creating the workload cluster with name "capz-e2e-ibeva2-win-vmss" using the "machine-pool-windows" template (Kubernetes v1.22.1, 1 control-plane machines, 1 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-e2e-ibeva2-win-vmss --infrastructure (default) --kubernetes-version v1.22.1 --control-plane-machine-count 1 --worker-machine-count 1 --flavor machine-pool-windows INFO: Applying the cluster template yaml to the cluster cluster.cluster.x-k8s.io/capz-e2e-ibeva2-win-vmss created azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-ibeva2-win-vmss created kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-ibeva2-win-vmss-control-plane created azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-ibeva2-win-vmss-control-plane created azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity created machinepool.cluster.x-k8s.io/capz-e2e-ibeva2-win-vmss-mp-0 created azuremachinepool.infrastructure.cluster.x-k8s.io/capz-e2e-ibeva2-win-vmss-mp-0 created kubeadmconfig.bootstrap.cluster.x-k8s.io/capz-e2e-ibeva2-win-vmss-mp-0 created machinepool.cluster.x-k8s.io/capz-e2e-ibeva2-win-vmss-mp-win created azuremachinepool.infrastructure.cluster.x-k8s.io/capz-e2e-ibeva2-win-vmss-mp-win created kubeadmconfig.bootstrap.cluster.x-k8s.io/capz-e2e-ibeva2-win-vmss-mp-win created clusterresourceset.addons.cluster.x-k8s.io/capz-e2e-ibeva2-win-vmss-flannel created configmap/cni-capz-e2e-ibeva2-win-vmss-flannel created INFO: Waiting for the cluster infrastructure to be provisioned �[1mSTEP�[0m: Waiting for cluster to enter the provisioned phase INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by capz-e2e-ibeva2/capz-e2e-ibeva2-win-vmss-control-plane to be provisioned �[1mSTEP�[0m: Waiting for one control plane node to exist INFO: Waiting for control plane to be ready INFO: Waiting for control plane capz-e2e-ibeva2/capz-e2e-ibeva2-win-vmss-control-plane to be ready (implies underlying nodes to be ready as well) �[1mSTEP�[0m: Waiting for the control plane to be ready INFO: Waiting for the machine deployments to be provisioned INFO: Waiting for the machine pools to be provisioned �[1mSTEP�[0m: Waiting for the machine pool workload nodes to exist �[1mSTEP�[0m: Dumping logs from the "capz-e2e-ibeva2-win-vmss" workload cluster �[1mSTEP�[0m: Dumping workload cluster capz-e2e-ibeva2/capz-e2e-ibeva2-win-vmss logs Apr 15 20:52:04.478: INFO: INFO: Collecting logs for node capz-e2e-ibeva2-win-vmss-control-plane-vdjmr in cluster capz-e2e-ibeva2-win-vmss in namespace capz-e2e-ibeva2 Apr 15 20:52:15.807: INFO: INFO: Collecting boot logs for AzureMachine capz-e2e-ibeva2-win-vmss-control-plane-vdjmr �[1mSTEP�[0m: Dumping workload cluster capz-e2e-ibeva2/capz-e2e-ibeva2-win-vmss kube-system pod logs �[1mSTEP�[0m: Fetching kube-system pod logs took 559.966255ms �[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-78fcd69978-czphf, container coredns �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-windows-lmwxg, container kube-proxy �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-ibeva2-win-vmss-control-plane-vdjmr, container kube-apiserver �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-ibeva2-win-vmss-control-plane-vdjmr, container kube-controller-manager �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-flannel-ds-amd64-6lzwl, container kube-flannel �[1mSTEP�[0m: Dumping workload cluster capz-e2e-ibeva2/capz-e2e-ibeva2-win-vmss Azure activity log �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-ibeva2-win-vmss-control-plane-vdjmr, container kube-scheduler �[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-78fcd69978-289mc, container coredns �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-flannel-ds-windows-amd64-9v9pm, container kube-flannel �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-4vrb9, container kube-proxy �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-nk7dr, container kube-proxy �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-flannel-ds-amd64-qnw2l, container kube-flannel �[1mSTEP�[0m: Creating log watcher for controller kube-system/etcd-capz-e2e-ibeva2-win-vmss-control-plane-vdjmr, container etcd �[1mSTEP�[0m: Fetching activity logs took 962.010257ms �[1mSTEP�[0m: Dumping all the Cluster API resources in the "capz-e2e-ibeva2" namespace �[1mSTEP�[0m: Deleting all clusters in the capz-e2e-ibeva2 namespace �[1mSTEP�[0m: Deleting cluster capz-e2e-ibeva2-win-vmss INFO: Waiting for the Cluster capz-e2e-ibeva2/capz-e2e-ibeva2-win-vmss to be deleted �[1mSTEP�[0m: Waiting for cluster capz-e2e-ibeva2-win-vmss to be deleted �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-ibeva2-win-vmss-control-plane-vdjmr, container kube-controller-manager: http2: client connection lost �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-qnw2l, container kube-flannel: http2: client connection lost �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/coredns-78fcd69978-czphf, container coredns: http2: client connection lost �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-flannel-ds-windows-amd64-9v9pm, container kube-flannel: http2: client connection lost �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-proxy-nk7dr, container kube-proxy: http2: client connection lost �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-proxy-4vrb9, container kube-proxy: http2: client connection lost �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/coredns-78fcd69978-289mc, container coredns: http2: client connection lost �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-proxy-windows-lmwxg, container kube-proxy: http2: client connection lost �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-ibeva2-win-vmss-control-plane-vdjmr, container kube-scheduler: http2: client connection lost �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-ibeva2-win-vmss-control-plane-vdjmr, container kube-apiserver: http2: client connection lost �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-6lzwl, container kube-flannel: http2: client connection lost �[1mSTEP�[0m: Got error while streaming logs for pod kube-system/etcd-capz-e2e-ibeva2-win-vmss-control-plane-vdjmr, container etcd: http2: client connection lost �[1mSTEP�[0m: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace capz-e2e-ibeva2 �[1mSTEP�[0m: Checking if any resources are left over in Azure for spec "create-workload-cluster" �[1mSTEP�[0m: Redacting sensitive information from logs INFO: "with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node" ran for 33m6s on Ginkgo node 3 of 3
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sWorkload\scluster\screation\sCreating\sa\sprivate\scluster\sCreates\sa\spublic\smanagement\scluster\sin\sthe\ssame\svnet$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:141 Expected success, but got an error: <*errors.withStack | 0xc001ca05e8>: { error: <*exec.ExitError | 0xc000bda7a0>{ ProcessState: { pid: 28057, status: 256, rusage: { Utime: {Sec: 0, Usec: 524123}, Stime: {Sec: 0, Usec: 164801}, Maxrss: 104912, Ixrss: 0, Idrss: 0, Isrss: 0, Minflt: 13643, Majflt: 1, Nswap: 0, Inblock: 256, Oublock: 25392, Msgsnd: 0, Msgrcv: 0, Nsignals: 0, Nvcsw: 4218, Nivcsw: 446, }, }, Stderr: nil, }, stack: [0x1819e9e, 0x181a565, 0x19839b7, 0x1b3c528, 0x1c9d968, 0x1cbebcc, 0x813b23, 0x82154a, 0x1cbf2db, 0x7fc603, 0x7fc21c, 0x7fb547, 0x8024ef, 0x801b92, 0x811491, 0x810fa7, 0x810797, 0x812ea6, 0x820bd8, 0x820916, 0x1cae6ba, 0x529ce5, 0x474781], } exit status 1 /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v0.4.8-0.20220215165403-0234afe87ffe/framework/clusterctl/clusterctl_helpers.go:272from junit.e2e_suite.2.xml
INFO: "Creates a public management cluster in the same vnet" started at Fri, 15 Apr 2022 19:39:11 UTC on Ginkgo node 2 of 3 �[1mSTEP�[0m: Creating namespace "capz-e2e-8s4l9o" for hosting the cluster Apr 15 19:39:11.826: INFO: starting to create namespace for hosting the "capz-e2e-8s4l9o" test spec 2022/04/15 19:39:11 failed trying to get namespace (capz-e2e-8s4l9o):namespaces "capz-e2e-8s4l9o" not found INFO: Creating namespace capz-e2e-8s4l9o INFO: Creating event watcher for namespace "capz-e2e-8s4l9o" Apr 15 19:39:11.913: INFO: Creating cluster identity secret %!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-8s4l9o-public-custom-vnet �[1mSTEP�[0m: creating Azure clients with the workload cluster's subscription �[1mSTEP�[0m: creating a resource group �[1mSTEP�[0m: creating a network security group �[1mSTEP�[0m: creating a node security group �[1mSTEP�[0m: creating a node routetable �[1mSTEP�[0m: creating a virtual network INFO: Creating the workload cluster with name "capz-e2e-8s4l9o-public-custom-vnet" using the "custom-vnet" template (Kubernetes v1.22.1, 1 control-plane machines, 1 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-e2e-8s4l9o-public-custom-vnet --infrastructure (default) --kubernetes-version v1.22.1 --control-plane-machine-count 1 --worker-machine-count 1 --flavor custom-vnet INFO: Applying the cluster template yaml to the cluster cluster.cluster.x-k8s.io/capz-e2e-8s4l9o-public-custom-vnet created azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-8s4l9o-public-custom-vnet created kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-8s4l9o-public-custom-vnet-control-plane created azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-8s4l9o-public-custom-vnet-control-plane created machinedeployment.cluster.x-k8s.io/capz-e2e-8s4l9o-public-custom-vnet-md-0 created azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-8s4l9o-public-custom-vnet-md-0 created kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-8s4l9o-public-custom-vnet-md-0 created azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity created machinehealthcheck.cluster.x-k8s.io/capz-e2e-8s4l9o-public-custom-vnet-mhc-0 created clusterresourceset.addons.cluster.x-k8s.io/capz-e2e-8s4l9o-public-custom-vnet-calico created configmap/cni-capz-e2e-8s4l9o-public-custom-vnet-calico created INFO: Waiting for the cluster infrastructure to be provisioned �[1mSTEP�[0m: Waiting for cluster to enter the provisioned phase INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by capz-e2e-8s4l9o/capz-e2e-8s4l9o-public-custom-vnet-control-plane to be provisioned �[1mSTEP�[0m: Waiting for one control plane node to exist INFO: Waiting for control plane to be ready INFO: Waiting for control plane capz-e2e-8s4l9o/capz-e2e-8s4l9o-public-custom-vnet-control-plane to be ready (implies underlying nodes to be ready as well) �[1mSTEP�[0m: Waiting for the control plane to be ready INFO: Waiting for the machine deployments to be provisioned �[1mSTEP�[0m: Waiting for the workload nodes to exist INFO: Waiting for the machine pools to be provisioned �[1mSTEP�[0m: checking that time synchronization is healthy on capz-e2e-8s4l9o-public-custom-vnet-control-plane-brx7p �[1mSTEP�[0m: checking that time synchronization is healthy on capz-e2e-8s4l9o-public-custom-vnet-md-0-2cf9x �[1mSTEP�[0m: creating a Kubernetes client to the workload cluster �[1mSTEP�[0m: Creating a namespace for hosting the azure-private-cluster test spec Apr 15 19:43:21.452: INFO: starting to create namespace for hosting the azure-private-cluster test spec INFO: Creating namespace capz-e2e-8s4l9o INFO: Creating event watcher for namespace "capz-e2e-8s4l9o" �[1mSTEP�[0m: Initializing the workload cluster INFO: clusterctl init --core cluster-api --bootstrap kubeadm --control-plane kubeadm --infrastructure azure INFO: Waiting for provider controllers to be running �[1mSTEP�[0m: Waiting for deployment capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager to be available INFO: Creating log watcher for controller capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager, pod capi-kubeadm-bootstrap-controller-manager-75467796c5-h4qjl, container manager �[1mSTEP�[0m: Waiting for deployment capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager to be available INFO: Creating log watcher for controller capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager, pod capi-kubeadm-control-plane-controller-manager-688b75d88d-mj4tx, container manager �[1mSTEP�[0m: Waiting for deployment capi-system/capi-controller-manager to be available INFO: Creating log watcher for controller capi-system/capi-controller-manager, pod capi-controller-manager-58757dd9b4-ffnm4, container manager �[1mSTEP�[0m: Waiting for deployment capz-system/capz-controller-manager to be available INFO: Creating log watcher for controller capz-system/capz-controller-manager, pod capz-controller-manager-6b89969fd9-d7jxg, container manager �[1mSTEP�[0m: Ensure public API server is stable before creating private cluster �[1mSTEP�[0m: Creating a private workload cluster INFO: Creating the workload cluster with name "capz-e2e-ii14gz-private" using the "private" template (Kubernetes v1.22.1, 3 control-plane machines, 1 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-e2e-ii14gz-private --infrastructure (default) --kubernetes-version v1.22.1 --control-plane-machine-count 3 --worker-machine-count 1 --flavor private INFO: Applying the cluster template yaml to the cluster Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "default.azurecluster.infrastructure.cluster.x-k8s.io": failed to call webhook: the server could not find the requested resource Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "default.azuremachinetemplate.infrastructure.cluster.x-k8s.io": failed to call webhook: the server could not find the requested resource Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "default.azuremachinetemplate.infrastructure.cluster.x-k8s.io": failed to call webhook: the server could not find the requested resource �[1mSTEP�[0m: Dumping logs from the "capz-e2e-8s4l9o-public-custom-vnet" workload cluster �[1mSTEP�[0m: Dumping workload cluster capz-e2e-8s4l9o/capz-e2e-8s4l9o-public-custom-vnet logs Apr 15 19:45:37.257: INFO: INFO: Collecting logs for node capz-e2e-8s4l9o-public-custom-vnet-control-plane-brx7p in cluster capz-e2e-8s4l9o-public-custom-vnet in namespace capz-e2e-8s4l9o Apr 15 19:45:43.583: INFO: INFO: Collecting boot logs for AzureMachine capz-e2e-8s4l9o-public-custom-vnet-control-plane-brx7p Apr 15 19:45:44.681: INFO: INFO: Collecting logs for node capz-e2e-8s4l9o-public-custom-vnet-md-0-2cf9x in cluster capz-e2e-8s4l9o-public-custom-vnet in namespace capz-e2e-8s4l9o Apr 15 19:45:54.554: INFO: INFO: Collecting boot logs for AzureMachine capz-e2e-8s4l9o-public-custom-vnet-md-0-2cf9x �[1mSTEP�[0m: Dumping workload cluster capz-e2e-8s4l9o/capz-e2e-8s4l9o-public-custom-vnet kube-system pod logs �[1mSTEP�[0m: Fetching kube-system pod logs took 323.388919ms �[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-kube-controllers-846b5f484d-rqt8q, container calico-kube-controllers �[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-78fcd69978-wc5vl, container coredns �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-8s4l9o-public-custom-vnet-control-plane-brx7p, container kube-controller-manager �[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-5jrrs, container calico-node �[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-gtqpk, container calico-node �[1mSTEP�[0m: Dumping workload cluster capz-e2e-8s4l9o/capz-e2e-8s4l9o-public-custom-vnet Azure activity log �[1mSTEP�[0m: Creating log watcher for controller kube-system/etcd-capz-e2e-8s4l9o-public-custom-vnet-control-plane-brx7p, container etcd �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-tl9fh, container kube-proxy �[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-78fcd69978-66678, container coredns �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-8s4l9o-public-custom-vnet-control-plane-brx7p, container kube-apiserver �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-8s4l9o-public-custom-vnet-control-plane-brx7p, container kube-scheduler �[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-88twf, container kube-proxy �[1mSTEP�[0m: Fetching activity logs took 576.37521ms �[1mSTEP�[0m: Dumping all the Cluster API resources in the "capz-e2e-8s4l9o" namespace �[1mSTEP�[0m: Deleting all clusters in the capz-e2e-8s4l9o namespace �[1mSTEP�[0m: Deleting cluster capz-e2e-8s4l9o-public-custom-vnet INFO: Waiting for the Cluster capz-e2e-8s4l9o/capz-e2e-8s4l9o-public-custom-vnet to be deleted �[1mSTEP�[0m: Waiting for cluster capz-e2e-8s4l9o-public-custom-vnet to be deleted W0415 19:50:56.735474 24147 reflector.go:436] pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167: watch of *v1.Event ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding I0415 19:51:28.006521 24147 trace.go:205] Trace[1720613000]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167 (15-Apr-2022 19:50:58.005) (total time: 30001ms): Trace[1720613000]: [30.001467568s] [30.001467568s] END E0415 19:51:28.006593 24147 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-8s4l9o-public-custom-vnet-934f9485.westus2.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-8s4l9o/events?resourceVersion=2406": dial tcp 40.91.77.218:6443: i/o timeout I0415 19:52:00.529129 24147 trace.go:205] Trace[1367505268]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167 (15-Apr-2022 19:51:30.527) (total time: 30001ms): Trace[1367505268]: [30.001405201s] [30.001405201s] END E0415 19:52:00.529189 24147 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-8s4l9o-public-custom-vnet-934f9485.westus2.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-8s4l9o/events?resourceVersion=2406": dial tcp 40.91.77.218:6443: i/o timeout I0415 19:52:36.491283 24147 trace.go:205] Trace[416891239]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167 (15-Apr-2022 19:52:06.489) (total time: 30001ms): Trace[416891239]: [30.001245444s] [30.001245444s] END E0415 19:52:36.491346 24147 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-8s4l9o-public-custom-vnet-934f9485.westus2.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-8s4l9o/events?resourceVersion=2406": dial tcp 40.91.77.218:6443: i/o timeout I0415 19:53:13.235407 24147 trace.go:205] Trace[1494307965]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167 (15-Apr-2022 19:52:43.234) (total time: 30000ms): Trace[1494307965]: [30.000987507s] [30.000987507s] END E0415 19:53:13.235469 24147 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-8s4l9o-public-custom-vnet-934f9485.westus2.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-8s4l9o/events?resourceVersion=2406": dial tcp 40.91.77.218:6443: i/o timeout I0415 19:54:06.413626 24147 trace.go:205] Trace[1135917625]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167 (15-Apr-2022 19:53:36.412) (total time: 30001ms): Trace[1135917625]: [30.001239462s] [30.001239462s] END E0415 19:54:06.413710 24147 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-8s4l9o-public-custom-vnet-934f9485.westus2.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-8s4l9o/events?resourceVersion=2406": dial tcp 40.91.77.218:6443: i/o timeout I0415 19:55:24.305370 24147 trace.go:205] Trace[1419763745]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167 (15-Apr-2022 19:54:54.303) (total time: 30001ms): Trace[1419763745]: [30.00168406s] [30.00168406s] END E0415 19:55:24.305443 24147 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-8s4l9o-public-custom-vnet-934f9485.westus2.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-8s4l9o/events?resourceVersion=2406": dial tcp 40.91.77.218:6443: i/o timeout E0415 19:56:16.264861 24147 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-8s4l9o-public-custom-vnet-934f9485.westus2.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-8s4l9o/events?resourceVersion=2406": dial tcp: lookup capz-e2e-8s4l9o-public-custom-vnet-934f9485.westus2.cloudapp.azure.com on 10.63.240.10:53: no such host �[1mSTEP�[0m: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace capz-e2e-8s4l9o �[1mSTEP�[0m: Running additional cleanup for the "create-workload-cluster" test spec Apr 15 19:56:16.479: INFO: deleting an existing virtual network "custom-vnet" Apr 15 19:56:27.132: INFO: deleting an existing route table "node-routetable" Apr 15 19:56:29.508: INFO: deleting an existing network security group "node-nsg" Apr 15 19:56:39.913: INFO: deleting an existing network security group "control-plane-nsg" Apr 15 19:56:50.263: INFO: verifying the existing resource group "capz-e2e-8s4l9o-public-custom-vnet" is empty Apr 15 19:56:50.348: INFO: deleting the existing resource group "capz-e2e-8s4l9o-public-custom-vnet" �[1mSTEP�[0m: Checking if any resources are left over in Azure for spec "create-workload-cluster" E0415 19:57:06.903289 24147 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-8s4l9o-public-custom-vnet-934f9485.westus2.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-8s4l9o/events?resourceVersion=2406": dial tcp: lookup capz-e2e-8s4l9o-public-custom-vnet-934f9485.westus2.cloudapp.azure.com on 10.63.240.10:53: no such host �[1mSTEP�[0m: Redacting sensitive information from logs INFO: "Creates a public management cluster in the same vnet" ran for 18m10s on Ginkgo node 2 of 3
Filter through log files | View test history on testgrid
capz-e2e Workload cluster creation Creating a GPU-enabled cluster with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating a VMSS cluster with a single control plane node and an AzureMachinePool with 2 nodes
capz-e2e Workload cluster creation Creating a Windows Enabled cluster With 3 control-plane nodes and 1 Linux worker node and 1 Windows worker node
capz-e2e Workload cluster creation Creating a cluster that uses the external cloud provider with a 1 control plane nodes and 2 worker nodes
capz-e2e Workload cluster creation Creating a ipv6 control-plane cluster With ipv6 worker node
capz-e2e Workload cluster creation Creating an AKS cluster with a single control plane node and 1 node
capz-e2e Workload cluster creation With 3 control-plane nodes and 2 worker nodes
capz-e2e Conformance Tests conformance-tests
capz-e2e Running the Cluster API E2E tests Running the KCP upgrade spec in a HA cluster Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd
capz-e2e Running the Cluster API E2E tests Running the KCP upgrade spec in a HA cluster using scale in rollout Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd
capz-e2e Running the Cluster API E2E tests Running the KCP upgrade spec in a single control plane cluster Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd
capz-e2e Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e Running the Cluster API E2E tests Should adopt up-to-date control plane Machines without modification Should adopt up-to-date control plane Machines without modification
capz-e2e Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e 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 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