PR #6004 - 04-13 07:50

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

151
Total Tests
128
Passed
4
Failed
19
Skipped

Failed Tests

TestNodePool
0s
TestNodePool/HostedCluster0
19m52.86s
hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-7vlj7/node-pool-n5jk5 in 2m8s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster node-pool-n5jk5 util.go:1978: Successfully waited for HostedCluster e2e-clusters-7vlj7/node-pool-n5jk5 to have valid conditions in 25ms hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
8m38.31s
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7vlj7/node-pool-n5jk5 in 1m4.025s util.go:235: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-n5jk5.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:281: Successfully waited for a successful connection to the guest API server in 17.55s util.go:462: Successfully waited for 0 nodes to become ready in 25ms util.go:1978: Successfully waited for HostedCluster e2e-clusters-7vlj7/node-pool-n5jk5 to have valid conditions in 7m11.025s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
200ms
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7vlj7/node-pool-n5jk5 in 25ms util.go:235: Successfully waited for kubeconfig secret to have data in 0s util.go:669: Container manager in pod cluster-api-77dd858745-6psqn has a restartCount > 0 (1)