PR #7795 - 02-26 07:28

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

337
Total Tests
298
Passed
3
Failed
36
Skipped

Failed Tests

TestAzureScheduler
29m3.74s
hypershift_framework.go:459: Successfully created hostedcluster e2e-clusters-c7qsm/azure-scheduler-fs4hg in 2m26s hypershift_framework.go:128: Summarizing unexpected conditions for HostedCluster azure-scheduler-fs4hg util.go:2974: Successfully waited for HostedCluster e2e-clusters-c7qsm/azure-scheduler-fs4hg to have valid conditions in 50ms hypershift_framework.go:278: skipping postTeardown() hypershift_framework.go:256: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
15m43.28s
util.go:291: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-c7qsm/azure-scheduler-fs4hg in 2m6.05s util.go:308: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-fs4hg.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:370: Successfully waited for a successful connection to the guest API server in 42.3s util.go:565: Successfully waited for 2 nodes to become ready in 8m57.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-c7qsm/azure-scheduler-fs4hg to rollout in 3m51.075s util.go:2974: Successfully waited for HostedCluster e2e-clusters-c7qsm/azure-scheduler-fs4hg to have valid conditions in 50ms
TestAzureScheduler/ValidateHostedCluster/EnsureNoCrashingPods
160ms
util.go:780: Container csi-snapshotter in pod azure-disk-csi-driver-controller-fd9ffd495-xz2nb has a restartCount > 0 (1)