Recent runs || View in Spyglass
PR | devigned: do not include customData in AzureMachinePool hash calculation |
Result | FAILURE |
Tests | 0 failed / 0 succeeded |
Started | |
Elapsed | 35m35s |
Revision | 3aeef19c2ccda264105106f4c9574085b5aa187e |
Refs |
1197 |
... skipping 452 lines ... [1mSTEP[0m: Fetching activity logs took 928.867976ms [1mSTEP[0m: Dumping all the Cluster API resources in the "create-workload-cluster-uggvdj" namespace [1mSTEP[0m: Deleting all clusters in the create-workload-cluster-uggvdj namespace [1mSTEP[0m: Deleting cluster capz-e2e-d3i9m0 INFO: Waiting for the Cluster create-workload-cluster-uggvdj/capz-e2e-d3i9m0 to be deleted [1mSTEP[0m: Waiting for cluster capz-e2e-d3i9m0 to be deleted [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-d3i9m0-control-plane-rshlh, container kube-apiserver: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-d3i9m0-control-plane-ngckn, container kube-apiserver: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/calico-node-8l44t, container calico-node: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-d3i9m0-control-plane-65ttq, container kube-apiserver: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-d3i9m0-control-plane-ngckn, container kube-scheduler: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-proxy-bzt69, container kube-proxy: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-gbw6x, container coredns: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-d3i9m0-control-plane-65ttq, container kube-controller-manager: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-d3i9m0-control-plane-ngckn, container kube-controller-manager: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-d3i9m0-control-plane-rshlh, container kube-scheduler: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/calico-node-djwdf, container calico-node: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/calico-node-wpsx8, container calico-node: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/etcd-capz-e2e-d3i9m0-control-plane-65ttq, container etcd: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-d3i9m0-control-plane-rshlh, container kube-controller-manager: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/etcd-capz-e2e-d3i9m0-control-plane-ngckn, container etcd: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-proxy-2lnps, container kube-proxy: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-d3i9m0-control-plane-65ttq, container kube-scheduler: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-proxy-kpg8d, container kube-proxy: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/kube-proxy-wkmk5, container kube-proxy: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/calico-node-dgvn6, container calico-node: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-l4cvx, container coredns: http2: client connection lost [1mSTEP[0m: Got error while streaming logs for pod kube-system/calico-kube-controllers-8f59968d4-gfml9, container calico-kube-controllers: http2: client connection lost [1mSTEP[0m: Deleting namespace used for hosting the "create-workload-cluster" test spec INFO: Deleting namespace create-workload-cluster-uggvdj [1mSTEP[0m: Redacting sensitive information from logs INFO: "With ipv6 worker node" ran for 23m3s on Ginkgo node 2 of 3 ... skipping 2 lines ... [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:39[0m Creating a ipv6 control-plane cluster [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:217[0m With ipv6 worker node [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:218[0m [90m------------------------------[0m {"component":"entrypoint","file":"prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2021-03-03T20:07:58Z"}