This job view page is being replaced by Spyglass soon. Check out the new job view.
PRnader-ziada: Use AzureClusterIdentity when running ci e2e tests
ResultFAILURE
Tests 4 failed / 6 succeeded
Started2021-07-01 18:06
Elapsed1h23m
Revision7f86f853726ccfc174135e61852ba0f0270a0649
Refs 1360

Test Failures


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 20m4s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sRunning\sthe\sCluster\sAPI\sE2E\stests\sRunning\sthe\sKCP\supgrade\sspec\sin\sa\sHA\scluster\sShould\ssuccessfully\supgrade\sKubernetes\,\sDNS\,\skube\-proxy\,\sand\setcd$'
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v0.4.0/e2e/kcp_upgrade.go:75
Timed out after 1200.000s.
Expected
    <string>: Provisioning
to equal
    <string>: Provisioned
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v0.4.0/framework/cluster_helpers.go:134
				
				Click to see stdout/stderrfrom junit.e2e_suite.3.xml

Filter through log files | View test history on testgrid


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 20m4s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sRunning\sthe\sCluster\sAPI\sE2E\stests\sRunning\sthe\sKCP\supgrade\sspec\sin\sa\ssingle\scontrol\splane\scluster\sShould\ssuccessfully\supgrade\sKubernetes\,\sDNS\,\skube\-proxy\,\sand\setcd$'
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v0.4.0/e2e/kcp_upgrade.go:75
Timed out after 1200.003s.
Expected
    <string>: Provisioning
to equal
    <string>: Provisioned
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v0.4.0/framework/cluster_helpers.go:134
				
				Click to see stdout/stderrfrom junit.e2e_suite.2.xml

Filter through log files | View test history on testgrid


capz-e2e Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster 20m4s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sRunning\sthe\sCluster\sAPI\sE2E\stests\sRunning\sthe\squick\-start\sspec\sShould\screate\sa\sworkload\scluster$'
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v0.4.0/e2e/quick_start.go:72
Timed out after 1200.001s.
Expected
    <string>: Provisioning
to equal
    <string>: Provisioned
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v0.4.0/framework/cluster_helpers.go:134
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation 23m2s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sRunning\sthe\sCluster\sAPI\sE2E\stests\sShould\ssuccessfully\sremediate\sunhealthy\smachines\swith\sMachineHealthCheck\sShould\ssuccessfully\strigger\sKCP\sremediation$'
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v0.4.0/e2e/mhc_remediations.go:101
Failed to get controller-runtime client
Unexpected error:
    <*url.Error | 0xc000ba4180>: {
        Op: "Get",
        URL: "https://mhc-remediation-n2azf7-2076875b.westus.cloudapp.azure.com:6443/api?timeout=32s",
        Err: <*http.httpError | 0xc00059ea20>{
            err: "net/http: request canceled (Client.Timeout exceeded while awaiting headers)",
            timeout: true,
        },
    }
    Get "https://mhc-remediation-n2azf7-2076875b.westus.cloudapp.azure.com:6443/api?timeout=32s": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
occurred
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v0.4.0/framework/cluster_proxy.go:171
				
				Click to see stdout/stderrfrom junit.e2e_suite.3.xml

Filter through log files | View test history on testgrid


Show 6 Passed Tests

Show 11 Skipped Tests