PR #6239 - 11-07 14:01

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

444
Total Tests
418
Passed
3
Failed
23
Skipped

Failed Tests

TestAutoscaling
1h12m9.09s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-tr5l9/autoscaling-b5r7w in 48s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-b5r7w util.go:2835: Successfully waited for HostedCluster e2e-clusters-tr5l9/autoscaling-b5r7w to have valid conditions in 0s hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestAutoscaling/Main
46m22.15s
TestAutoscaling/Main/TestAutoscaling
35m45.06s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-tr5l9/autoscaling-b5r7w in 0s util.go:297: Successfully waited for kubeconfig secret to have data in 0s util.go:359: Successfully waited for a successful connection to the guest API server in 0s util.go:541: Successfully waited for 1 nodes to become ready in 0s autoscaling_test.go:107: Enabled autoscaling. Namespace: e2e-clusters-tr5l9, name: autoscaling-b5r7w-us-east-1a, min: 1, max: 3 autoscaling_test.go:126: Created workload. Node: ip-10-0-11-99.ec2.internal, memcapacity: 6760168Ki util.go:541: Successfully waited for 3 nodes to become ready in 5m45s autoscaling_test.go:146: Deleted workload eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:541: Failed to wait for 1 nodes to become ready 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 2