PR #7081 - 11-04 11:57

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

442
Total Tests
411
Passed
7
Failed
24
Skipped

Failed Tests

TestAutoscaling
1h7m5.77s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-mvpp6/autoscaling-229w8 in 1m6s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-229w8 util.go:2835: Successfully waited for HostedCluster e2e-clusters-mvpp6/autoscaling-229w8 to have valid conditions in 0s hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestAutoscaling/Main
45m7.17s
TestAutoscaling/Main/TestAutoscaling
35m9.07s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mvpp6/autoscaling-229w8 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-mvpp6, name: autoscaling-229w8-us-east-1a, min: 1, max: 3 autoscaling_test.go:126: Created workload. Node: ip-10-0-7-72.ec2.internal, memcapacity: 6760160Ki util.go:541: Successfully waited for 3 nodes to become ready in 5m9s 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
TestUpgradeControlPlane
35m50.91s
control_plane_upgrade_test.go:26: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-w64m1833/release@sha256:f63b524ddbfbb11c174cd808f85caad71ec1258f79d8d02fb614852e37f6fba0, toImage: registry.build01.ci.openshift.org/ci-op-w64m1833/release@sha256:ce1e47e3b15b0f08df2c81730a4fb71f4247ccb65e176d3bb0385bc40d05c7ef hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-8q2qj/control-plane-upgrade-v4qtf in 52s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-v4qtf util.go:2835: Successfully waited for HostedCluster e2e-clusters-8q2qj/control-plane-upgrade-v4qtf to have valid conditions in 0s hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestUpgradeControlPlane/EnsureHostedCluster
1.08s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8q2qj/control-plane-upgrade-v4qtf 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:2835: Successfully waited for HostedCluster e2e-clusters-8q2qj/control-plane-upgrade-v4qtf to have valid conditions in 0s
TestUpgradeControlPlane/EnsureHostedCluster/EnsureNetworkPolicies
270ms
TestUpgradeControlPlane/EnsureHostedCluster/EnsureNetworkPolicies/EnsureLimitedEgressTrafficToManagementKAS
260ms
util.go:1133: Connecting to kubernetes endpoint on: https://172.20.0.1:6443 util.go:1164: cluster api pod was unexpectedly not allowed to reach the management KAS. stdOut: . stdErr: unable to upgrade connection: container not found ("manager")