Failed Tests
hypershift_framework.go:513: Successfully created hostedcluster e2e-clusters-r4k8z/azure-scheduler-v2qs5 in 2m22s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster azure-scheduler-v2qs5
util.go:3036: Successfully waited for HostedCluster e2e-clusters-r4k8z/azure-scheduler-v2qs5 to have valid conditions in 25ms
hypershift_framework.go:332: skipping postTeardown()
hypershift_framework.go:310: skipping teardown, already called
util.go:297: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-r4k8z/azure-scheduler-v2qs5 in 1m39.025s
util.go:314: Successfully waited for kubeconfig secret to have data in 25ms
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-v2qs5.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout
eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-v2qs5.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF
util.go:376: Successfully waited for a successful connection to the guest API server in 57.45s
util.go:571: Successfully waited for 2 nodes to become ready in 8m54.075s
util.go:608: Successfully waited for HostedCluster e2e-clusters-r4k8z/azure-scheduler-v2qs5 to rollout in 3m0.025s
util.go:3036: Successfully waited for HostedCluster e2e-clusters-r4k8z/azure-scheduler-v2qs5 to have valid conditions in 25ms
util.go:817: Container manager in pod cluster-api-84798b49d5-pkpjr has a restartCount > 0 (1)