PR #5792 - 04-18 11:48

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

101
Total Tests
73
Passed
10
Failed
18
Skipped

Failed Tests

TestAzureScheduler
1h2m38.84s
hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-n4h7v/azure-scheduler-rlf75 in 1m34s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster azure-scheduler-rlf75 util.go:2123: Successfully waited for HostedCluster e2e-clusters-n4h7v/azure-scheduler-rlf75 to have valid conditions in 25ms hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called
TestAzureScheduler/Main
30m0.17s
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-n4h7v/azure-scheduler-rlf75 in 25ms util.go:235: Successfully waited for kubeconfig secret to have data in 0s util.go:281: Successfully waited for a successful connection to the guest API server in 0s util.go:462: Successfully waited for 2 nodes to become ready in 25ms azure_scheduler_test.go:111: Updated clusterSizingConfig. azure_scheduler_test.go:158: Successfully waited for HostedCluster size label and annotations updated in 25ms azure_scheduler_test.go:150: Scaled Nodepool. Namespace: e2e-clusters-n4h7v, name: azure-scheduler-rlf75, replicas: 0xc0029f982c eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 3 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 3 nodes, got 2
TestNodePool
0s
TestNodePool/HostedCluster0
1h2m46.29s
hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-gt2dl/node-pool-b9jjx in 1m39s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster node-pool-b9jjx eventually.go:104: Failed to get *v1beta1.HostedCluster: client rate limiter Wait returned an error: context deadline exceeded util.go:2123: Failed to wait for HostedCluster e2e-clusters-gt2dl/node-pool-b9jjx to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-gt2dl/node-pool-b9jjx invalid at RV 50473 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 4.19.0-0.ci-2025-04-18-115749-test-ci-op-f5gz5rzr-latest) eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 4.19.0-0.ci-2025-04-18-115749-test-ci-op-f5gz5rzr-latest) hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called
TestNodePool/HostedCluster0/Main
70ms
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-gt2dl/node-pool-b9jjx in 25ms util.go:235: Successfully waited for kubeconfig secret to have data in 25ms util.go:281: Successfully waited for a successful connection to the guest API server in 25ms
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigGetsRolledOut
42m15.17s
nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest util.go:462: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-ntomachineconfig-replace in 21m39.025s nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-ntomachineconfig-replace to have correct status in 17.025s util.go:378: Successfully waited for NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-ntomachineconfig-replace to start config update in 19.025s eventually.go:104: Failed to get *v1beta1.NodePool: client rate limiter Wait returned an error: context deadline exceeded util.go:393: Failed to wait for NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-ntomachineconfig-replace to finish config update in 20m0s: context deadline exceeded eventually.go:224: observed *v1beta1.NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-ntomachineconfig-replace invalid at RV 42819 after 20m0s: incorrect condition: wanted UpdatingConfig=False, got UpdatingConfig=True: AsExpected(Updating config in progress. Target config: 41dde9ad) util.go:393: *v1beta1.NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-ntomachineconfig-replace conditions: util.go:393: UpdateManagementEnabled=True: AsExpected util.go:393: ValidArchPlatform=True: AsExpected util.go:393: ReconciliationActive=True: ReconciliationActive(Reconciliation active on resource) util.go:393: ValidMachineConfig=True: AsExpected util.go:393: UpdatingVersion=False: AsExpected util.go:393: ValidGeneratedPayload=True: AsExpected(Payload generated successfully) util.go:393: AllMachinesReady=False: Creating(2 of 4 machines are not ready Machine node-pool-b9jjx-test-ntomachineconfig-replace-8khq2-lz7ht: Creating: virtualmachine creating or updating Machine node-pool-b9jjx-test-ntomachineconfig-replace-8khq2-vfsc7: Creating: virtualmachine creating or updating ) util.go:393: AllNodesHealthy=False: WaitingForNodeRef(Machine node-pool-b9jjx-test-ntomachineconfig-replace-8khq2-lz7ht: WaitingForNodeRef Machine node-pool-b9jjx-test-ntomachineconfig-replace-8khq2-vfsc7: WaitingForNodeRef ) util.go:393: AutoscalingEnabled=False: AsExpected util.go:393: ValidReleaseImage=True: AsExpected(Using release image: registry.build01.ci.openshift.org/ci-op-f5gz5rzr/release@sha256:85905fe2713de15f7c443c8da35c8fe5fdd0f803b3b4ae3d195a83fc5576f1c8) util.go:393: UpdatingConfig=True: AsExpected(Updating config in progress. Target config: 41dde9ad) util.go:393: ReachedIgnitionEndpoint=False: ignitionNotReached util.go:393: ValidTuningConfig=True: AsExpected util.go:393: UpdatingPlatformMachineTemplate=False: AsExpected util.go:393: AutorepairEnabled=False: AsExpected util.go:393: Ready=True: AsExpected
TestNodePool/HostedCluster0/Main/TestNodePoolReplaceUpgrade
41m57.27s
nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest util.go:462: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-replaceupgrade in 21m35.025s nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-replaceupgrade to have correct status in 12.025s nodepool_upgrade_test.go:160: Validating all Nodes have the synced labels and taints nodepool_upgrade_test.go:163: Successfully waited for NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-replaceupgrade to have version 4.19.0-0.ci-2025-04-17-160508 in 25ms nodepool_upgrade_test.go:180: Updating NodePool image. Image: registry.build01.ci.openshift.org/ci-op-f5gz5rzr/release@sha256:85905fe2713de15f7c443c8da35c8fe5fdd0f803b3b4ae3d195a83fc5576f1c8 nodepool_upgrade_test.go:187: Successfully waited for NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-replaceupgrade to start the upgrade in 8.025s nodepool_upgrade_test.go:200: Failed to wait for NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-replaceupgrade to have version 4.19.0-0.ci-2025-04-18-115749-test-ci-op-f5gz5rzr-latest in 20m0s: context deadline exceeded eventually.go:224: observed *v1beta1.NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-replaceupgrade invalid at RV 40832 after 20m0s: eventually.go:227: - wanted version 4.19.0-0.ci-2025-04-18-115749-test-ci-op-f5gz5rzr-latest, got 4.19.0-0.ci-2025-04-17-160508 eventually.go:227: - incorrect condition: wanted UpdatingVersion=False, got UpdatingVersion=True: AsExpected(Updating version in progress. Target version: 4.19.0-0.ci-2025-04-18-115749-test-ci-op-f5gz5rzr-latest) nodepool_upgrade_test.go:200: *v1beta1.NodePool e2e-clusters-gt2dl/node-pool-b9jjx-test-replaceupgrade conditions: nodepool_upgrade_test.go:200: ReconciliationActive=True: ReconciliationActive(Reconciliation active on resource) nodepool_upgrade_test.go:200: ValidMachineConfig=True: AsExpected nodepool_upgrade_test.go:200: UpdatingConfig=False: AsExpected nodepool_upgrade_test.go:200: UpdatingVersion=True: AsExpected(Updating version in progress. Target version: 4.19.0-0.ci-2025-04-18-115749-test-ci-op-f5gz5rzr-latest) nodepool_upgrade_test.go:200: ValidGeneratedPayload=True: AsExpected(Payload generated successfully) nodepool_upgrade_test.go:200: ReachedIgnitionEndpoint=False: ignitionNotReached nodepool_upgrade_test.go:200: AutoscalingEnabled=False: AsExpected nodepool_upgrade_test.go:200: UpdateManagementEnabled=True: AsExpected nodepool_upgrade_test.go:200: ValidArchPlatform=True: AsExpected nodepool_upgrade_test.go:200: AllMachinesReady=False: Creating(1 of 2 machines are not ready Machine node-pool-b9jjx-test-replaceupgrade-4cqnc-4rhhn: Creating: virtualmachine creating or updating ) nodepool_upgrade_test.go:200: AllNodesHealthy=False: WaitingForNodeRef(Machine node-pool-b9jjx-test-replaceupgrade-4cqnc-4rhhn: WaitingForNodeRef ) nodepool_upgrade_test.go:200: ValidReleaseImage=True: AsExpected(Using release image: registry.build01.ci.openshift.org/ci-op-f5gz5rzr/release@sha256:85905fe2713de15f7c443c8da35c8fe5fdd0f803b3b4ae3d195a83fc5576f1c8) nodepool_upgrade_test.go:200: ValidTuningConfig=True: AsExpected nodepool_upgrade_test.go:200: UpdatingPlatformMachineTemplate=False: AsExpected nodepool_upgrade_test.go:200: AutorepairEnabled=False: AsExpected nodepool_upgrade_test.go:200: Ready=True: AsExpected
TestNodePool/HostedCluster2
49m55.54s
hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-2hq7h/node-pool-h5s5k in 1m30s hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster node-pool-h5s5k util.go:2123: Successfully waited for HostedCluster e2e-clusters-2hq7h/node-pool-h5s5k to have valid conditions in 25ms hypershift_framework.go:194: skipping postTeardown() hypershift_framework.go:175: skipping teardown, already called
TestNodePool/HostedCluster2/Main
80ms
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2hq7h/node-pool-h5s5k in 25ms util.go:235: Successfully waited for kubeconfig secret to have data in 0s util.go:281: Successfully waited for a successful connection to the guest API server in 25ms
TestNodePool/HostedCluster2/Main/TestAdditionalTrustBundlePropagation
30m0.02s
nodepool_additionalTrustBundlePropagation_test.go:36: Starting AdditionalTrustBundlePropagationTest. eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:462: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-2hq7h/node-pool-h5s5k-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