This job view page is being replaced by Spyglass soon. Check out the new job view.
PRnader-ziada: Don't useExperimentalRetryJoin
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-02-25 14:14
Elapsed37m52s
Revision95c894f40e6a3e970013c265415df571e0a3d1ca
Refs 1029

No Test Failures!


Error lines from build-log.txt

... skipping 452 lines ...
STEP: Fetching activity logs took 1.052148241s
STEP: Dumping all the Cluster API resources in the "create-workload-cluster-xftr8t" namespace
STEP: Deleting all clusters in the create-workload-cluster-xftr8t namespace
STEP: Deleting cluster capz-e2e-t9t6tq
INFO: Waiting for the Cluster create-workload-cluster-xftr8t/capz-e2e-t9t6tq to be deleted
STEP: Waiting for cluster capz-e2e-t9t6tq to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-t9t6tq-control-plane-4626x, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-t9t6tq-control-plane-9dx2h, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-t9t6tq-control-plane-qzk9z, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-t9t6tq-control-plane-qzk9z, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-8f59968d4-sp2f7, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-t9t6tq-control-plane-qzk9z, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-tbl8r, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-t9t6tq-control-plane-9dx2h, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-n7crn, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-zd8v7, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-fktj9, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-6bltv, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-t9t6tq-control-plane-4626x, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-7t68k, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-t9t6tq-control-plane-4626x, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-rz4kn, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-t9t6tq-control-plane-9dx2h, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-pjz6g, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-587wf, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-t9t6tq-control-plane-4626x, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-t9t6tq-control-plane-9dx2h, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-t9t6tq-control-plane-qzk9z, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-f9fd979d6-kvfp8, container coredns: http2: client connection lost
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace create-workload-cluster-xftr8t
STEP: Redacting sensitive information from logs
INFO: "With ipv6 worker node" ran for 22m34s on Ginkgo node 2 of 3


... skipping 2 lines ...
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:39
  Creating a ipv6 control-plane cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:217
    With ipv6 worker node
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:218
------------------------------
{"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-02-25T14:52:14Z"}