Failed Tests
hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-qj9zs/node-pool-6sz76 in 1m52s
hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster node-pool-6sz76
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-qj9zs/node-pool-6sz76 to have valid conditions in 2s: context deadline exceeded
eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-qj9zs/node-pool-6sz76 invalid at RV 36843 after 2s:
eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion
eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 4.19.0-0.ci-2025-04-14-205749-test-ci-op-5y8btxfx-latest)
eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 4.19.0-0.ci-2025-04-14-205749-test-ci-op-5y8btxfx-latest)
hypershift_framework.go:194: skipping postTeardown()
hypershift_framework.go:175: skipping teardown, already called
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qj9zs/node-pool-6sz76 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 50ms
nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest
util.go:462: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-inplace in 17m57.025s
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-inplace to have correct status in 7.025s
util.go:378: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-inplace to start config update in 12.025s
util.go:393: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-inplace to finish config update in 7m8.025s
nodepool_machineconfig_test.go:166: Successfully waited for all pods in the DaemonSet kube-system/node-pool-6sz76-test-ntomachineconfig-inplace to be ready in 50ms
util.go:462: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-inplace in 25ms
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-inplace to have correct status in 25ms
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qj9zs/node-pool-6sz76 in 25ms
util.go:235: Successfully waited for kubeconfig secret to have data in 0s
util.go:669: Container manager in pod capi-provider-5c6bc44c8b-mpqkd has a restartCount > 0 (1)
nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest
util.go:462: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-replace in 17m49.025s
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-replace to have correct status in 9.025s
util.go:378: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-replace to start config update in 14.025s
util.go:393: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-replace to finish config update in 8m39.025s
nodepool_machineconfig_test.go:166: Successfully waited for all pods in the DaemonSet kube-system/node-pool-6sz76-test-ntomachineconfig-replace to be ready in 25ms
util.go:462: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-replace in 0s
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-ntomachineconfig-replace to have correct status in 0s
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qj9zs/node-pool-6sz76 in 25ms
util.go:235: Successfully waited for kubeconfig secret to have data in 0s
util.go:669: Container manager in pod capi-provider-5c6bc44c8b-mpqkd has a restartCount > 0 (1)
nodepool_machineconfig_test.go:55: Starting test NodePoolMachineconfigRolloutTest
util.go:462: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-machineconfig in 17m47.025s
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-machineconfig to have correct status in 10.025s
util.go:378: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-machineconfig to start config update in 8.025s
util.go:393: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-machineconfig to finish config update in 8m28.025s
nodepool_machineconfig_test.go:166: Successfully waited for all pods in the DaemonSet kube-system/machineconfig-update-checker-replace to be ready in 50ms
util.go:462: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-machineconfig in 0s
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-qj9zs/node-pool-6sz76-test-machineconfig to have correct status in 25ms
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qj9zs/node-pool-6sz76 in 25ms
util.go:235: Successfully waited for kubeconfig secret to have data in 0s
util.go:669: Container manager in pod capi-provider-5c6bc44c8b-mpqkd has a restartCount > 0 (1)