Failed Tests
hypershift_framework.go:317: Successfully created hostedcluster e2e-clusters-x46w7/node-pool-jhqwn in 2m36s
hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster node-pool-jhqwn
util.go:2166: Failed to wait for HostedCluster e2e-clusters-x46w7/node-pool-jhqwn to have valid conditions in 2s: context deadline exceeded
eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-x46w7/node-pool-jhqwn invalid at RV 86015 after 2s:
eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 4.20.0-0.ci-2025-05-29-135722-test-ci-op-6264vd4k-latest)
eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: ClusterOperatorsDegraded(Error while reconciling 4.20.0-0.ci-2025-05-29-135722-test-ci-op-6264vd4k-latest: dns, node-tuning has an unknown error: ClusterOperatorsDegraded)
hypershift_framework.go:195: skipping postTeardown()
hypershift_framework.go:176: skipping teardown, already called
util.go:219: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-x46w7/node-pool-jhqwn in 25ms
util.go:236: Successfully waited for kubeconfig secret to have data in 25ms
util.go:282: Successfully waited for a successful connection to the guest API server in 25ms
nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest
eventually.go:258: Failed to get **v1.Node: Get "https://api-node-pool-jhqwn.aks-e2e.hypershift.azure.devcluster.openshift.com:443/api/v1/nodes?labelSelector=hypershift.openshift.io%2FnodePool%3Dnode-pool-jhqwn-test-ntomachineconfig-inplace": dial tcp 20.57.83.58:443: connect: connection refused
util.go:463: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-inplace in 17m41.175s
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-inplace to have correct status in 15.025s
util.go:379: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-inplace to start config update in 25.025s
util.go:394: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-inplace to finish config update in 8m6.025s
nodepool_machineconfig_test.go:166: Successfully waited for all pods in the DaemonSet kube-system/node-pool-jhqwn-test-ntomachineconfig-inplace to be ready in 1s
util.go:463: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-inplace in 25ms
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-inplace to have correct status in 6.025s
util.go:219: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-x46w7/node-pool-jhqwn in 25ms
util.go:236: Successfully waited for kubeconfig secret to have data in 0s
util.go:662: Container manager in pod capi-provider-5495b867cb-xjgfv has a restartCount > 0 (1)
nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest
util.go:463: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-replace in 7m16.1s
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-replace to have correct status in 10.025s
util.go:379: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-replace to start config update in 20.025s
util.go:394: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-replace to finish config update in 18m47.025s
nodepool_machineconfig_test.go:166: Successfully waited for all pods in the DaemonSet kube-system/node-pool-jhqwn-test-ntomachineconfig-replace to be ready in 25ms
util.go:463: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-replace in 50ms
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-ntomachineconfig-replace to have correct status in 25ms
util.go:219: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-x46w7/node-pool-jhqwn in 25ms
util.go:236: Successfully waited for kubeconfig secret to have data in 25ms
util.go:662: Container manager in pod capi-provider-5495b867cb-xjgfv has a restartCount > 0 (1)
nodepool_machineconfig_test.go:55: Starting test NodePoolMachineconfigRolloutTest
util.go:463: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-machineconfig in 15m11.1s
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-machineconfig to have correct status in 15.075s
util.go:379: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-machineconfig to start config update in 15.025s
util.go:394: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-machineconfig to finish config update in 12m11.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:463: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-machineconfig in 0s
nodepool_test.go:350: Successfully waited for NodePool e2e-clusters-x46w7/node-pool-jhqwn-test-machineconfig to have correct status in 25ms
util.go:219: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-x46w7/node-pool-jhqwn in 25ms
util.go:236: Successfully waited for kubeconfig secret to have data in 25ms
util.go:662: Container manager in pod capi-provider-5495b867cb-xjgfv has a restartCount > 0 (1)