PR #8751 - 07-13 14:41

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

566
Total Tests
526
Passed
10
Failed
30
Skipped

Failed Tests

TestCreateClusterRequestServingIsolation
1h5m1.64s
requestserving.go:105: Created request serving nodepool clusters/273d720bfb-mgmt-reqserving-r9cz5 requestserving.go:105: Created request serving nodepool clusters/273d720bfb-mgmt-reqserving-56249 requestserving.go:113: Created non request serving nodepool clusters/273d720bfb-mgmt-non-reqserving-bwlzs requestserving.go:113: Created non request serving nodepool clusters/273d720bfb-mgmt-non-reqserving-rt98s requestserving.go:113: Created non request serving nodepool clusters/273d720bfb-mgmt-non-reqserving-7jz4x util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/273d720bfb-mgmt-reqserving-r9cz5 in 4m42s util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/273d720bfb-mgmt-reqserving-56249 in 3s util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/273d720bfb-mgmt-non-reqserving-bwlzs in 1m30s util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/273d720bfb-mgmt-non-reqserving-rt98s in 0s util.go:583: Successfully waited for 1 nodes to become ready for NodePool clusters/273d720bfb-mgmt-non-reqserving-7jz4x in 0s create_cluster_test.go:299: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-wn6fb/request-serving-isolation-l6jw5 in 11s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster request-serving-isolation-l6jw5 util.go:3158: Successfully waited for HostedCluster e2e-clusters-wn6fb/request-serving-isolation-l6jw5 to have valid conditions in 0s hypershift_framework.go:349: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/273d720bfb-mgmt-reqserving-r9cz5 requestserving.go:132: Tearing down custom nodepool clusters/273d720bfb-mgmt-reqserving-56249 requestserving.go:132: Tearing down custom nodepool clusters/273d720bfb-mgmt-non-reqserving-bwlzs requestserving.go:132: Tearing down custom nodepool clusters/273d720bfb-mgmt-non-reqserving-rt98s requestserving.go:132: Tearing down custom nodepool clusters/273d720bfb-mgmt-non-reqserving-7jz4x hypershift_framework.go:327: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
48m15.04s
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wn6fb/request-serving-isolation-l6jw5 in 1m6s util.go:322: Successfully waited for kubeconfig secret to have data in 0s eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-l6jw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-l6jw5.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-l6jw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.207.82.65:443: i/o timeout eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-l6jw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.2.106.86:443: i/o timeout util.go:384: Successfully waited for a successful connection to the guest API server in 2m9.025s util.go:583: Failed to wait for 3 nodes to become ready in 45m0s: context deadline exceeded eventually.go:384: observed invalid **v1.Node state after 45m0s eventually.go:401: - observed **v1.Node collection invalid: expected 3 nodes, got 2
TestKarpenterUpgradeControlPlane
37m13.97s
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-qlphx/karpenter-upgrade-control-plane-9dzk5 in 50s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster karpenter-upgrade-control-plane-9dzk5 util.go:3158: Successfully waited for HostedCluster e2e-clusters-qlphx/karpenter-upgrade-control-plane-9dzk5 to have valid conditions in 0s hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called
TestKarpenterUpgradeControlPlane/ValidateHostedCluster
26m38.48s
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qlphx/karpenter-upgrade-control-plane-9dzk5 in 2m48s util.go:322: Successfully waited for kubeconfig secret to have data in 0s eventually.go:105: Failed to get *v1.SelfSubjectReview: Post "https://api-karpenter-upgrade-control-plane-9dzk5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.167.219.91:443: i/o timeout util.go:384: Successfully waited for a successful connection to the guest API server in 30.025s util.go:583: Successfully waited for 2 nodes to become ready in 16m42s util.go:620: Successfully waited for HostedCluster e2e-clusters-qlphx/karpenter-upgrade-control-plane-9dzk5 to rollout in 3m27s util.go:3158: Successfully waited for HostedCluster e2e-clusters-qlphx/karpenter-upgrade-control-plane-9dzk5 to have valid conditions in 3m6s
TestKarpenterUpgradeControlPlane/ValidateHostedCluster/EnsureNoCrashingPods
60ms
util.go:829: Container aws-ebs-csi-driver-operator in pod aws-ebs-csi-driver-operator-869dcbc7f4-l8hqk has a restartCount > 0 (1) util.go:826: Leader election failure detected in container manager in pod capi-provider-54ff546964-fxg9v util.go:826: Leader election failure detected in container control-plane-operator in pod control-plane-operator-747db894d9-tf8rn
TestNodePool
0s
TestNodePool/HostedCluster0
1h21m14.75s
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-tqmpw/node-pool-7svh6 in 24s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-7svh6 util.go:3158: Failed to wait for HostedCluster e2e-clusters-tqmpw/node-pool-7svh6 to have valid conditions in 2s: context deadline exceeded eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-tqmpw/node-pool-7svh6 invalid at RV 145796 after 2s: eventually.go:228: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion eventually.go:228: - incorrect condition: wanted ControlPlaneConnectionAvailable=Unknown, got ControlPlaneConnectionAvailable=True: AsExpected(All is well) eventually.go:228: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 5.0.0-0.ci-2026-07-13-145713-test-ci-op-2isn1z05-latest) eventually.go:228: - incorrect condition: wanted DataPlaneConnectionAvailable=Unknown, got DataPlaneConnectionAvailable=True: AsExpected(All is well) eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 5.0.0-0.ci-2026-07-13-145713-test-ci-op-2isn1z05-latest) hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called
TestNodePool/HostedCluster0/Main
20ms
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-tqmpw/node-pool-7svh6 in 0s util.go:322: Successfully waited for kubeconfig secret to have data in 0s util.go:384: Successfully waited for a successful connection to the guest API server in 0s
TestNodePool/HostedCluster0/Main/TestKMSRootVolumeEncryption
29m34s
nodepool_kms_root_volume_test.go:43: Starting test KMSRootVolumeTest nodepool_kms_root_volume_test.go:55: retrieved KMS ARN: arn:aws:kms:us-east-1:820196288204:key/d3cdd9e0-3fd1-47a4-a559-72ae3672c5a6 nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-tqmpw/node-pool-7svh6-test-kms-root-volume in 9m30s eventually.go:105: Failed to get *v1beta1.NodePool: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline nodepool_test.go:431: Failed to wait for NodePool e2e-clusters-tqmpw/node-pool-7svh6-test-kms-root-volume to have correct status in 20m0s: context deadline exceeded eventually.go:225: observed *v1beta1.NodePool e2e-clusters-tqmpw/node-pool-7svh6-test-kms-root-volume invalid at RV 96672 after 20m0s: incorrect condition: wanted ReachedIgnitionEndpoint=True, got ReachedIgnitionEndpoint=False: ignitionNotReached
TestNodePool/HostedCluster0/Main/TestNodePoolDay2Tags
45m4s
nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=InstanceProvisionStarted util.go:583: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-tqmpw/node-pool-7svh6-test-day2-tags in 45m0s: context deadline exceeded eventually.go:384: observed invalid **v1.Node state after 45m0s eventually.go:401: - observed **v1.Node collection invalid: expected 1 nodes, got 0