PR #6202 - 05-30 13:33

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

145
Total Tests
117
Passed
4
Failed
24
Skipped

Failed Tests

TestNodePool
0s
TestNodePool/HostedCluster2
46m8.3s
hypershift_framework.go:317: Successfully created hostedcluster e2e-clusters-rldnw/node-pool-p4mx7 in 2m27s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster node-pool-p4mx7 util.go:2166: Successfully waited for HostedCluster e2e-clusters-rldnw/node-pool-p4mx7 to have valid conditions in 25ms hypershift_framework.go:195: skipping postTeardown() hypershift_framework.go:176: skipping teardown, already called
TestNodePool/HostedCluster2/Main
120ms
util.go:219: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-rldnw/node-pool-p4mx7 in 25ms util.go:236: Successfully waited for kubeconfig secret to have data in 0s util.go:282: Successfully waited for a successful connection to the guest API server in 75ms
TestNodePool/HostedCluster2/Main/TestAdditionalTrustBundlePropagation
30m0.01s
nodepool_additionalTrustBundlePropagation_test.go:36: Starting AdditionalTrustBundlePropagationTest. eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:463: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-rldnw/node-pool-p4mx7-test-additional-trust-bundle-propagation in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 1 nodes, got 0