This job view page is being replaced by Spyglass soon. Check out the new job view.
PRjsturtevant: Handle WindowsHostProcess feature gates for versions running in CI
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-10-22 22:48
Elapsed1h29m
Revisionc108d0cf54a913b1b9abc90e4fdccdc1edb6f7cb
Refs 1790

No Test Failures!


Error lines from build-log.txt

... skipping 489 lines ...
STEP: Fetching activity logs took 645.137449ms
STEP: Dumping all the Cluster API resources in the "quick-start-ksh8qg" namespace
STEP: Deleting cluster quick-start-ksh8qg/quick-start-ots1fp
STEP: Deleting cluster quick-start-ots1fp
INFO: Waiting for the Cluster quick-start-ksh8qg/quick-start-ots1fp to be deleted
STEP: Waiting for cluster quick-start-ots1fp to be deleted
STEP: Got error while streaming logs for pod kube-system/etcd-quick-start-ots1fp-control-plane-bxbsq, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-vclhz, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-tpxj4, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-quick-start-ots1fp-control-plane-bxbsq, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-xx5hz, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-846b5f484d-dzmlc, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-j8hnh, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-quick-start-ots1fp-control-plane-bxbsq, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-quick-start-ots1fp-control-plane-bxbsq, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-m7d9m, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-wmkr7, container kube-proxy: http2: client connection lost
STEP: Deleting namespace used for hosting the "quick-start" test spec
INFO: Deleting namespace quick-start-ksh8qg
STEP: Redacting sensitive information from logs


• [SLOW TEST:795.010 seconds]
... skipping 207 lines ...
Running the Cluster API E2E tests Running the self-hosted spec 
  Should pivot the bootstrap cluster to a self-hosted cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_selfhosted.go:103

STEP: Creating namespace "self-hosted" for hosting the cluster
Oct 22 23:17:19.432: INFO: starting to create namespace for hosting the "self-hosted" test spec
2021/10/22 23:17:19 failed trying to get namespace (self-hosted):namespaces "self-hosted" not found
INFO: Creating namespace self-hosted
INFO: Creating event watcher for namespace "self-hosted"
STEP: Creating a workload cluster
INFO: Creating the workload cluster with name "self-hosted-ar735u" using the "(default)" template (Kubernetes v1.22.1, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster self-hosted-ar735u --infrastructure (default) --kubernetes-version v1.22.1 --control-plane-machine-count 1 --worker-machine-count 1 --flavor (default)
... skipping 260 lines ...
STEP: Creating log watcher for controller kube-system/kube-scheduler-mhc-remediation-1kchgw-control-plane-rc9w6, container kube-scheduler
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-t8z8v, container coredns
STEP: Creating log watcher for controller kube-system/kube-proxy-mzzbk, container kube-proxy
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-846b5f484d-d7vhx, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/kube-apiserver-mhc-remediation-1kchgw-control-plane-rc9w6, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-controller-manager-mhc-remediation-1kchgw-control-plane-rc9w6, container kube-controller-manager
STEP: Error starting logs stream for pod kube-system/calico-node-j5g2s, container calico-node: container "calico-node" in pod "calico-node-j5g2s" is waiting to start: PodInitializing
STEP: Fetching activity logs took 537.840084ms
STEP: Dumping all the Cluster API resources in the "mhc-remediation-wz4y2f" namespace
STEP: Deleting cluster mhc-remediation-wz4y2f/mhc-remediation-1kchgw
STEP: Deleting cluster mhc-remediation-1kchgw
INFO: Waiting for the Cluster mhc-remediation-wz4y2f/mhc-remediation-1kchgw to be deleted
STEP: Waiting for cluster mhc-remediation-1kchgw to be deleted
... skipping 97 lines ...
STEP: Creating log watcher for controller kube-system/calico-node-7tg56, container calico-node
STEP: Creating log watcher for controller kube-system/kube-controller-manager-kcp-upgrade-4o879d-control-plane-968j8, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-apiserver-kcp-upgrade-4o879d-control-plane-575kj, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-controller-manager-kcp-upgrade-4o879d-control-plane-575kj, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-controller-manager-kcp-upgrade-4o879d-control-plane-kbxwp, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-proxy-4hfmh, container kube-proxy
STEP: Got error while iterating over activity logs for resource group capz-e2e-fwrfoe: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.001257064s
STEP: Dumping all the Cluster API resources in the "kcp-upgrade-u5ykmc" namespace
STEP: Deleting cluster kcp-upgrade-u5ykmc/kcp-upgrade-4o879d
STEP: Deleting cluster kcp-upgrade-4o879d
INFO: Waiting for the Cluster kcp-upgrade-u5ykmc/kcp-upgrade-4o879d to be deleted
STEP: Waiting for cluster kcp-upgrade-4o879d to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-kcp-upgrade-4o879d-control-plane-968j8, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-kcp-upgrade-4o879d-control-plane-kbxwp, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-wrzch, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-hpf5m, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-fp9tw, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-7tg56, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-kcp-upgrade-4o879d-control-plane-kbxwp, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-kcp-upgrade-4o879d-control-plane-968j8, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-lvrgp, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-kcp-upgrade-4o879d-control-plane-kbxwp, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-846b5f484d-m85sj, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-sv4ls, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-kcp-upgrade-4o879d-control-plane-968j8, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-kcp-upgrade-4o879d-control-plane-968j8, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-l88d5, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-kcp-upgrade-4o879d-control-plane-kbxwp, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-cntff, container kube-proxy: http2: client connection lost
STEP: Deleting namespace used for hosting the "kcp-upgrade" test spec
INFO: Deleting namespace kcp-upgrade-u5ykmc
STEP: Redacting sensitive information from logs


• [SLOW TEST:3027.558 seconds]
... skipping 166 lines ...
STEP: Fetching activity logs took 1.131395031s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-coyet2" namespace
STEP: Deleting cluster mhc-remediation-coyet2/mhc-remediation-b2v88d
STEP: Deleting cluster mhc-remediation-b2v88d
INFO: Waiting for the Cluster mhc-remediation-coyet2/mhc-remediation-b2v88d to be deleted
STEP: Waiting for cluster mhc-remediation-b2v88d to be deleted
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-vdsst, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-b2v88d-control-plane-9fcrg, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-b2v88d-control-plane-g4dpj, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-5hhms, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-kjnsz, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-b2v88d-control-plane-xmvh7, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-846b5f484d-ck9sm, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-b2v88d-control-plane-g4dpj, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-gkbpf, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-b2v88d-control-plane-9fcrg, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-b2v88d-control-plane-9fcrg, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-hv794, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-2tdvt, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-b2v88d-control-plane-9fcrg, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-b2v88d-control-plane-xmvh7, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-b2v88d-control-plane-xmvh7, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-b2v88d-control-plane-xmvh7, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-b2v88d-control-plane-g4dpj, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-b2v88d-control-plane-g4dpj, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-gnqjt, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-hgwh5, container kube-proxy: http2: client connection lost
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
INFO: Deleting namespace mhc-remediation-coyet2
STEP: Redacting sensitive information from logs


• [SLOW TEST:1420.379 seconds]
... skipping 8 lines ...