PR #8819 - 06-24 14:08

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

397
Total Tests
338
Passed
12
Failed
47
Skipped

Failed Tests

TestNodePool
0s
TestNodePool/HostedCluster0
1h47m46.83s
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-b669k/node-pool-fgkcb in 2m42s hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-fgkcb util.go:3140: Failed to wait for HostedCluster e2e-clusters-b669k/node-pool-fgkcb to have valid conditions in 2s: context deadline exceeded eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-b669k/node-pool-fgkcb invalid at RV 118630 after 2s: eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 5.0.0-0.ci-2026-06-24-142144-test-ci-op-b0wf3f3m-latest) eventually.go:228: - incorrect condition: wanted DataPlaneConnectionAvailable=Unknown, got DataPlaneConnectionAvailable=True: AsExpected(All is well) eventually.go:228: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion eventually.go:228: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 5.0.0-0.ci-2026-06-24-142144-test-ci-op-b0wf3f3m-latest) eventually.go:228: - incorrect condition: wanted ControlPlaneConnectionAvailable=Unknown, got ControlPlaneConnectionAvailable=True: AsExpected(All is well) hypershift_framework.go:349: skipping postTeardown() hypershift_framework.go:327: skipping teardown, already called
TestNodePool/HostedCluster0/Main
150ms
util.go:305: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b669k/node-pool-fgkcb in 50ms util.go:322: Successfully waited for kubeconfig secret to have data in 25ms util.go:384: Successfully waited for a successful connection to the guest API server in 25ms
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigAppliedInPlace
45m13.02s
nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest nodepool_test.go:369: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:505: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:505: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure eventually.go:259: Failed to get **v1.Node: context deadline exceeded util.go:583: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-b669k/node-pool-fgkcb-test-ntomachineconfig-inplace in 45m0s: context deadline exceeded eventually.go:384: observed invalid **v1.Node state after 45m0s eventually.go:401: - observed **v1.Node collection invalid: expected 2 nodes, got 0
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigGetsRolledOut
45m13.02s
nodepool_nto_machineconfig_test.go:67: Starting test NTOMachineConfigRolloutTest nodepool_test.go:369: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:505: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:505: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure util.go:583: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-b669k/node-pool-fgkcb-test-ntomachineconfig-replace in 45m0s: context deadline exceeded eventually.go:384: observed invalid **v1.Node state after 45m0s eventually.go:401: - observed **v1.Node /node-pool-fgkcb-test-ntomachineconfig-replace-cd4qs-79q8n invalid: incorrect condition: wanted Ready=True, got Ready=False: KubeletNotReady(container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: no CNI configuration file in /etc/kubernetes/cni/net.d/. Has your network provider started?) util.go:583: *v1.Node /node-pool-fgkcb-test-ntomachineconfig-replace-cd4qs-79q8n conditions: util.go:583: MemoryPressure=False: KubeletHasSufficientMemory(kubelet has sufficient memory available) util.go:583: DiskPressure=False: KubeletHasNoDiskPressure(kubelet has no disk pressure) util.go:583: PIDPressure=False: KubeletHasSufficientPID(kubelet has sufficient PID available) util.go:583: Ready=False: KubeletNotReady(container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: no CNI configuration file in /etc/kubernetes/cni/net.d/. Has your network provider started?)
TestNodePool/HostedCluster0/Main/TestNTOPerformanceProfile
45m15.63s
nodepool_nto_performanceprofile_test.go:59: Starting test NTOPerformanceProfileTest nodepool_test.go:369: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:505: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:505: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure eventually.go:259: Failed to get **v1.Node: context deadline exceeded util.go:583: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-b669k/node-pool-fgkcb-test-ntoperformanceprofile 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
TestNodePool/HostedCluster0/Main/TestNodePoolInPlaceUpgrade
45m13.23s
nodepool_upgrade_test.go:99: starting test NodePoolUpgradeTest nodepool_test.go:369: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:505: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:505: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure eventually.go:259: Failed to get **v1.Node: Get "https://api-node-pool-fgkcb.aks-e2e.hypershift.azure.devcluster.openshift.com:443/api/v1/nodes?labelSelector=hypershift.openshift.io%2FnodePool%3Dnode-pool-fgkcb-test-inplaceupgrade": context deadline exceeded util.go:583: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-b669k/node-pool-fgkcb-test-inplaceupgrade 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
TestNodePool/HostedCluster0/Main/TestNodePoolPrevReleaseN1
45m13.22s
nodepool_prev_release_test.go:33: Starting NodePoolPrevReleaseCreateTest. nodepool_test.go:369: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:505: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:505: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure eventually.go:259: Failed to get **v1.Node: context deadline exceeded util.go:583: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-b669k/node-pool-fgkcb-rfbg6 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
TestNodePool/HostedCluster0/Main/TestNodePoolPrevReleaseN2
45m18.22s
nodepool_prev_release_test.go:33: Starting NodePoolPrevReleaseCreateTest. nodepool_test.go:369: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:505: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:505: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure util.go:583: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-b669k/node-pool-fgkcb-nr4k6 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
TestNodePool/HostedCluster0/Main/TestNodePoolPrevReleaseN3
45m12.92s
nodepool_prev_release_test.go:33: Starting NodePoolPrevReleaseCreateTest. nodepool_test.go:369: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:505: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:505: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure eventually.go:259: Failed to get **v1.Node: context deadline exceeded util.go:583: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-b669k/node-pool-fgkcb-j82zk 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
TestNodePool/HostedCluster0/Main/TestNodePoolReplaceUpgrade
1h22m53.57s
nodepool_upgrade_test.go:99: starting test NodePoolUpgradeTest nodepool_test.go:369: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:505: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:505: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure util.go:583: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-b669k/node-pool-fgkcb-test-replaceupgrade in 37m30.025s nodepool_test.go:429: Successfully waited for NodePool e2e-clusters-b669k/node-pool-fgkcb-test-replaceupgrade to have correct status in 75ms nodepool_upgrade_test.go:177: Validating all Nodes have the synced labels and taints nodepool_upgrade_test.go:180: Successfully waited for NodePool e2e-clusters-b669k/node-pool-fgkcb-test-replaceupgrade to have version 5.0.0-0.ci-2026-06-23-155404 in 25ms nodepool_upgrade_test.go:195: Validating NodesInfo is populated with version 5.0.0-0.ci-2026-06-23-155404 before upgrade nodepool_upgrade_test.go:196: Successfully waited for NodePool e2e-clusters-b669k/node-pool-fgkcb-test-replaceupgrade to have NodesInfo with version 5.0.0-0.ci-2026-06-23-155404 in 25ms nodepool_upgrade_test.go:218: Updating NodePool image. Image: registry.build01.ci.openshift.org/ci-op-b0wf3f3m/release@sha256:c28d9e2a09dba14150d587d9d9251d366b7d211708bde16fa8fdf4481996f4a5 nodepool_upgrade_test.go:225: Successfully waited for NodePool e2e-clusters-b669k/node-pool-fgkcb-test-replaceupgrade to start the upgrade in 3.025s eventually.go:105: Failed to get *v1beta1.NodePool: client rate limiter Wait returned an error: context deadline exceeded nodepool_upgrade_test.go:238: Failed to wait for NodePool e2e-clusters-b669k/node-pool-fgkcb-test-replaceupgrade to have version 5.0.0-0.ci-2026-06-24-142144-test-ci-op-b0wf3f3m-latest in 45m0s: context deadline exceeded eventually.go:225: observed *v1beta1.NodePool e2e-clusters-b669k/node-pool-fgkcb-test-replaceupgrade invalid at RV 109683 after 45m0s: eventually.go:228: - wanted version 5.0.0-0.ci-2026-06-24-142144-test-ci-op-b0wf3f3m-latest, got 5.0.0-0.ci-2026-06-23-155404 eventually.go:228: - incorrect condition: wanted UpdatingVersion=False, got UpdatingVersion=True: AsExpected(Updating version in progress. Target version: 5.0.0-0.ci-2026-06-24-142144-test-ci-op-b0wf3f3m-latest) nodepool_upgrade_test.go:238: *v1beta1.NodePool e2e-clusters-b669k/node-pool-fgkcb-test-replaceupgrade conditions: nodepool_upgrade_test.go:238: AutoscalingEnabled=False: AsExpected nodepool_upgrade_test.go:238: UpdateManagementEnabled=True: AsExpected nodepool_upgrade_test.go:238: ValidReleaseImage=True: AsExpected(Using release image: registry.build01.ci.openshift.org/ci-op-b0wf3f3m/release@sha256:c28d9e2a09dba14150d587d9d9251d366b7d211708bde16fa8fdf4481996f4a5) nodepool_upgrade_test.go:238: ValidArchPlatform=True: AsExpected nodepool_upgrade_test.go:238: ReconciliationActive=True: ReconciliationActive(Reconciliation active on resource) nodepool_upgrade_test.go:238: SupportedVersionSkew=True: AsExpected(Release image version is valid) nodepool_upgrade_test.go:238: ValidMachineConfig=True: AsExpected nodepool_upgrade_test.go:238: UpdatingConfig=False: AsExpected nodepool_upgrade_test.go:238: UpdatingVersion=True: AsExpected(Updating version in progress. Target version: 5.0.0-0.ci-2026-06-24-142144-test-ci-op-b0wf3f3m-latest) nodepool_upgrade_test.go:238: ValidGeneratedPayload=Unknown(Unable to get status data from token secret) nodepool_upgrade_test.go:238: ReachedIgnitionEndpoint=False: ignitionNotReached nodepool_upgrade_test.go:238: AllMachinesReady=True: AsExpected(All is well) nodepool_upgrade_test.go:238: AllNodesHealthy=False: NodeProvisioning(1 of 2 machines are not healthy Machine node-pool-fgkcb-test-replaceupgrade-tt67x-nj5pb: NodeProvisioning: Waiting for a node with matching ProviderID to exist ) nodepool_upgrade_test.go:238: ValidPlatformConfig=True: AsExpected(All is well) nodepool_upgrade_test.go:238: ValidTuningConfig=True: AsExpected nodepool_upgrade_test.go:238: UpdatingPlatformMachineTemplate=False: AsExpected nodepool_upgrade_test.go:238: AutorepairEnabled=False: AsExpected nodepool_upgrade_test.go:238: Ready=True: AsExpected
TestNodePool/HostedCluster0/Main/TestNodepoolMachineconfigGetsRolledout
45m24.33s
nodepool_machineconfig_test.go:54: Starting test NodePoolMachineconfigRolloutTest nodepool_test.go:369: Validating CAPI v1 condition message bubbling during machine provisioning nodepool_test.go:505: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef nodepool_test.go:505: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure eventually.go:259: Failed to get **v1.Node: context deadline exceeded util.go:583: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-b669k/node-pool-fgkcb-test-machineconfig 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