periodic-cluster-api-provider-azure-e2e-full-v1alpha4 #1520850073078992896
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 2 failed / 7 succeeded |
| Started | |
| Elapsed | 1h45m |
| Revision | release-0.5 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sWorkload\scluster\screation\sCreating\sa\sGPU\-enabled\scluster\swith\sa\ssingle\scontrol\splane\snode\sand\s1\snode$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:377
Timed out after 1200.002s.
Expected
<bool>: false
to be true
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_gpu.go:76
INFO: "with a single control plane node and 1 node" started at Sun, 01 May 2022 20:04:45 UTC on Ginkgo node 2 of 3
�[1mSTEP�[0m: Creating namespace "capz-e2e-di2vm6" for hosting the cluster
May 1 20:04:45.794: INFO: starting to create namespace for hosting the "capz-e2e-di2vm6" test spec
2022/05/01 20:04:45 failed trying to get namespace (capz-e2e-di2vm6):namespaces "capz-e2e-di2vm6" not found
INFO: Creating namespace capz-e2e-di2vm6
INFO: Creating event watcher for namespace "capz-e2e-di2vm6"
May 1 20:04:45.866: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-di2vm6-gpu
INFO: Creating the workload cluster with name "capz-e2e-di2vm6-gpu" using the "nvidia-gpu" template (Kubernetes v1.22.1, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster capz-e2e-di2vm6-gpu --infrastructure (default) --kubernetes-version v1.22.1 --control-plane-machine-count 1 --worker-machine-count 1 --flavor nvidia-gpu
INFO: Applying the cluster template yaml to the cluster
cluster.cluster.x-k8s.io/capz-e2e-di2vm6-gpu serverside-applied
azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-di2vm6-gpu serverside-applied
kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-di2vm6-gpu-control-plane serverside-applied
azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-di2vm6-gpu-control-plane serverside-applied
azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity serverside-applied
machinedeployment.cluster.x-k8s.io/capz-e2e-di2vm6-gpu-md-0 serverside-applied
azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-di2vm6-gpu-md-0 serverside-applied
kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-di2vm6-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
clusterresourceset.addons.cluster.x-k8s.io/capz-e2e-di2vm6-gpu-calico serverside-applied
configmap/cni-capz-e2e-di2vm6-gpu-calico serverside-applied
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-di2vm6/capz-e2e-di2vm6-gpu-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-di2vm6/capz-e2e-di2vm6-gpu-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: creating a Kubernetes client to the workload cluster
�[1mSTEP�[0m: Waiting for a node to have an "nvidia.com/gpu" allocatable resource
�[1mSTEP�[0m: Dumping logs from the "capz-e2e-di2vm6-gpu" workload cluster
�[1mSTEP�[0m: Dumping workload cluster capz-e2e-di2vm6/capz-e2e-di2vm6-gpu logs
May 1 20:29:58.259: INFO: INFO: Collecting logs for node capz-e2e-di2vm6-gpu-control-plane-ctfd7 in cluster capz-e2e-di2vm6-gpu in namespace capz-e2e-di2vm6
May 1 20:30:24.807: INFO: INFO: Collecting boot logs for AzureMachine capz-e2e-di2vm6-gpu-control-plane-ctfd7
May 1 20:30:26.175: INFO: INFO: Collecting logs for node capz-e2e-di2vm6-gpu-md-0-4g4p2 in cluster capz-e2e-di2vm6-gpu in namespace capz-e2e-di2vm6
May 1 20:30:48.721: INFO: INFO: Collecting boot logs for AzureMachine capz-e2e-di2vm6-gpu-md-0-4g4p2
�[1mSTEP�[0m: Dumping workload cluster capz-e2e-di2vm6/capz-e2e-di2vm6-gpu kube-system pod logs
�[1mSTEP�[0m: Fetching kube-system pod logs took 704.852338ms
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-kube-controllers-846b5f484d-l65l8, container calico-kube-controllers
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-di2vm6-gpu-control-plane-ctfd7, container kube-controller-manager
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-8k6xv, container kube-proxy
�[1mSTEP�[0m: Dumping workload cluster capz-e2e-di2vm6/capz-e2e-di2vm6-gpu Azure activity log
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-gz659, container kube-proxy
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-b67mj, container calico-node
�[1mSTEP�[0m: Creating log watcher for controller kube-system/etcd-capz-e2e-di2vm6-gpu-control-plane-ctfd7, container etcd
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-di2vm6-gpu-control-plane-ctfd7, container kube-scheduler
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-di2vm6-gpu-control-plane-ctfd7, container kube-apiserver
�[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-78fcd69978-2hwhz, container coredns
�[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-78fcd69978-p68bh, container coredns
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-j8csp, container calico-node
�[1mSTEP�[0m: Fetching activity logs took 1.00997171s
�[1mSTEP�[0m: Dumping all the Cluster API resources in the "capz-e2e-di2vm6" namespace
�[1mSTEP�[0m: Deleting all clusters in the capz-e2e-di2vm6 namespace
�[1mSTEP�[0m: Deleting cluster capz-e2e-di2vm6-gpu
INFO: Waiting for the Cluster capz-e2e-di2vm6/capz-e2e-di2vm6-gpu to be deleted
�[1mSTEP�[0m: Waiting for cluster capz-e2e-di2vm6-gpu to be deleted
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-proxy-gz659, container kube-proxy: http2: client connection lost
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-di2vm6-gpu-control-plane-ctfd7, container kube-controller-manager: http2: client connection lost
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-proxy-8k6xv, container kube-proxy: http2: client connection lost
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/calico-kube-controllers-846b5f484d-l65l8, container calico-kube-controllers: http2: client connection lost
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/calico-node-b67mj, container calico-node: http2: client connection lost
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-di2vm6-gpu-control-plane-ctfd7, container kube-apiserver: http2: client connection lost
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/coredns-78fcd69978-2hwhz, container coredns: http2: client connection lost
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/etcd-capz-e2e-di2vm6-gpu-control-plane-ctfd7, container etcd: http2: client connection lost
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-di2vm6-gpu-control-plane-ctfd7, container kube-scheduler: http2: client connection lost
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/coredns-78fcd69978-p68bh, container coredns: http2: client connection lost
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/calico-node-j8csp, container calico-node: http2: client connection lost
�[1mSTEP�[0m: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace capz-e2e-di2vm6
�[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 1 node" ran for 33m42s on Ginkgo node 2 of 3
from junit.e2e_suite.2.xml
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 | 0xc000694f00>: {
error: <*exec.ExitError | 0xc001e129c0>{
ProcessState: {
pid: 28248,
status: 256,
rusage: {
Utime: {Sec: 0, Usec: 560473},
Stime: {Sec: 0, Usec: 151912},
Maxrss: 100228,
Ixrss: 0,
Idrss: 0,
Isrss: 0,
Minflt: 12199,
Majflt: 0,
Nswap: 0,
Inblock: 0,
Oublock: 25392,
Msgsnd: 0,
Msgrcv: 0,
Nsignals: 0,
Nvcsw: 4583,
Nivcsw: 335,
},
},
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:272
INFO: "Creates a public management cluster in the same vnet" started at Sun, 01 May 2022 19:45:10 UTC on Ginkgo node 1 of 3
�[1mSTEP�[0m: Creating namespace "capz-e2e-alb3wj" for hosting the cluster
May 1 19:45:10.097: INFO: starting to create namespace for hosting the "capz-e2e-alb3wj" test spec
2022/05/01 19:45:10 failed trying to get namespace (capz-e2e-alb3wj):namespaces "capz-e2e-alb3wj" not found
INFO: Creating namespace capz-e2e-alb3wj
INFO: Creating event watcher for namespace "capz-e2e-alb3wj"
May 1 19:45:10.150: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-alb3wj-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-alb3wj-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-alb3wj-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-alb3wj-public-custom-vnet created
azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-alb3wj-public-custom-vnet created
kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-alb3wj-public-custom-vnet-control-plane created
azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-alb3wj-public-custom-vnet-control-plane created
machinedeployment.cluster.x-k8s.io/capz-e2e-alb3wj-public-custom-vnet-md-0 created
azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-alb3wj-public-custom-vnet-md-0 created
kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-alb3wj-public-custom-vnet-md-0 created
azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity created
machinehealthcheck.cluster.x-k8s.io/capz-e2e-alb3wj-public-custom-vnet-mhc-0 created
clusterresourceset.addons.cluster.x-k8s.io/capz-e2e-alb3wj-public-custom-vnet-calico created
configmap/cni-capz-e2e-alb3wj-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-alb3wj/capz-e2e-alb3wj-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-alb3wj/capz-e2e-alb3wj-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-alb3wj-public-custom-vnet-control-plane-dbgnf
�[1mSTEP�[0m: checking that time synchronization is healthy on capz-e2e-alb3wj-public-custom-vnet-md-0-r7x6v
�[1mSTEP�[0m: creating a Kubernetes client to the workload cluster
�[1mSTEP�[0m: Creating a namespace for hosting the azure-private-cluster test spec
May 1 19:50:12.284: INFO: starting to create namespace for hosting the azure-private-cluster test spec
INFO: Creating namespace capz-e2e-alb3wj
INFO: Creating event watcher for namespace "capz-e2e-alb3wj"
�[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-xtwgn, 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-545sk, 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-mcmt8, 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-5f7c5d5586-l72rn, 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-cpe6mj-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-cpe6mj-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-alb3wj-public-custom-vnet" workload cluster
�[1mSTEP�[0m: Dumping workload cluster capz-e2e-alb3wj/capz-e2e-alb3wj-public-custom-vnet logs
May 1 19:53:58.425: INFO: INFO: Collecting logs for node capz-e2e-alb3wj-public-custom-vnet-control-plane-dbgnf in cluster capz-e2e-alb3wj-public-custom-vnet in namespace capz-e2e-alb3wj
May 1 19:54:07.314: INFO: INFO: Collecting boot logs for AzureMachine capz-e2e-alb3wj-public-custom-vnet-control-plane-dbgnf
May 1 19:54:08.753: INFO: INFO: Collecting logs for node capz-e2e-alb3wj-public-custom-vnet-md-0-r7x6v in cluster capz-e2e-alb3wj-public-custom-vnet in namespace capz-e2e-alb3wj
May 1 19:54:22.011: INFO: INFO: Collecting boot logs for AzureMachine capz-e2e-alb3wj-public-custom-vnet-md-0-r7x6v
�[1mSTEP�[0m: Dumping workload cluster capz-e2e-alb3wj/capz-e2e-alb3wj-public-custom-vnet kube-system pod logs
�[1mSTEP�[0m: Fetching kube-system pod logs took 580.039882ms
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-alb3wj-public-custom-vnet-control-plane-dbgnf, container kube-controller-manager
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-txvlv, container kube-proxy
�[1mSTEP�[0m: Creating log watcher for controller kube-system/etcd-capz-e2e-alb3wj-public-custom-vnet-control-plane-dbgnf, container etcd
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-kube-controllers-846b5f484d-jcvfk, container calico-kube-controllers
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-fgbsw, container calico-node
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-khgj4, container calico-node
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-alb3wj-public-custom-vnet-control-plane-dbgnf, container kube-apiserver
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-alb3wj-public-custom-vnet-control-plane-dbgnf, container kube-scheduler
�[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-78fcd69978-d7dw8, container coredns
�[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-78fcd69978-rfzq4, container coredns
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-ftjrq, container kube-proxy
�[1mSTEP�[0m: Dumping workload cluster capz-e2e-alb3wj/capz-e2e-alb3wj-public-custom-vnet Azure activity log
�[1mSTEP�[0m: Fetching activity logs took 558.641735ms
�[1mSTEP�[0m: Dumping all the Cluster API resources in the "capz-e2e-alb3wj" namespace
�[1mSTEP�[0m: Deleting all clusters in the capz-e2e-alb3wj namespace
�[1mSTEP�[0m: Deleting cluster capz-e2e-alb3wj-public-custom-vnet
INFO: Waiting for the Cluster capz-e2e-alb3wj/capz-e2e-alb3wj-public-custom-vnet to be deleted
�[1mSTEP�[0m: Waiting for cluster capz-e2e-alb3wj-public-custom-vnet to be deleted
W0501 19:59:25.782146 24258 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
I0501 19:59:56.992087 24258 trace.go:205] Trace[171695247]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167 (01-May-2022 19:59:26.990) (total time: 30001ms):
Trace[171695247]: [30.001064577s] [30.001064577s] END
E0501 19:59:56.992151 24258 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-alb3wj-public-custom-vnet-d3bd9d61.uksouth.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-alb3wj/events?resourceVersion=2702": dial tcp 20.90.192.173:6443: i/o timeout
I0501 20:00:29.461105 24258 trace.go:205] Trace[743877956]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167 (01-May-2022 19:59:59.460) (total time: 30000ms):
Trace[743877956]: [30.000687134s] [30.000687134s] END
E0501 20:00:29.461162 24258 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-alb3wj-public-custom-vnet-d3bd9d61.uksouth.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-alb3wj/events?resourceVersion=2702": dial tcp 20.90.192.173:6443: i/o timeout
I0501 20:01:03.882154 24258 trace.go:205] Trace[1899414511]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167 (01-May-2022 20:00:33.880) (total time: 30001ms):
Trace[1899414511]: [30.001230399s] [30.001230399s] END
E0501 20:01:03.882218 24258 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-alb3wj-public-custom-vnet-d3bd9d61.uksouth.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-alb3wj/events?resourceVersion=2702": dial tcp 20.90.192.173:6443: i/o timeout
I0501 20:01:45.545820 24258 trace.go:205] Trace[1313838182]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167 (01-May-2022 20:01:15.544) (total time: 30001ms):
Trace[1313838182]: [30.001273982s] [30.001273982s] END
E0501 20:01:45.545908 24258 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-alb3wj-public-custom-vnet-d3bd9d61.uksouth.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-alb3wj/events?resourceVersion=2702": dial tcp 20.90.192.173:6443: i/o timeout
�[1mSTEP�[0m: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace capz-e2e-alb3wj
�[1mSTEP�[0m: Running additional cleanup for the "create-workload-cluster" test spec
May 1 20:02:34.257: INFO: deleting an existing virtual network "custom-vnet"
I0501 20:02:34.503435 24258 trace.go:205] Trace[497670784]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.21.4/tools/cache/reflector.go:167 (01-May-2022 20:02:04.502) (total time: 30001ms):
Trace[497670784]: [30.001115038s] [30.001115038s] END
E0501 20:02:34.503509 24258 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-alb3wj-public-custom-vnet-d3bd9d61.uksouth.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-alb3wj/events?resourceVersion=2702": dial tcp 20.90.192.173:6443: i/o timeout
May 1 20:02:45.350: INFO: deleting an existing route table "node-routetable"
May 1 20:02:47.963: INFO: deleting an existing network security group "node-nsg"
May 1 20:02:58.864: INFO: deleting an existing network security group "control-plane-nsg"
May 1 20:03:09.447: INFO: verifying the existing resource group "capz-e2e-alb3wj-public-custom-vnet" is empty
May 1 20:03:09.595: INFO: deleting the existing resource group "capz-e2e-alb3wj-public-custom-vnet"
E0501 20:03:11.192976 24258 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-alb3wj-public-custom-vnet-d3bd9d61.uksouth.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-alb3wj/events?resourceVersion=2702": dial tcp: lookup capz-e2e-alb3wj-public-custom-vnet-d3bd9d61.uksouth.cloudapp.azure.com on 10.63.240.10:53: no such host
�[1mSTEP�[0m: Checking if any resources are left over in Azure for spec "create-workload-cluster"
�[1mSTEP�[0m: Redacting sensitive information from logs
INFO: "Creates a public management cluster in the same vnet" ran for 18m33s on Ginkgo node 1 of 3
from junit.e2e_suite.1.xml
Filter through log files | View test history on testgrid
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 Windows enabled VMSS cluster with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 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