PR #7137 - 11-05 11:28

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

98
Total Tests
46
Passed
26
Failed
26
Skipped

Failed Tests

TestAutoscaling
46m27.27s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-nvhl6/autoscaling-qzh5b in 2m20s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-qzh5b util.go:2835: Failed to wait for HostedCluster e2e-clusters-nvhl6/autoscaling-qzh5b to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-nvhl6/autoscaling-qzh5b invalid at RV 33305 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=False, got ClusterVersionProgressing=True: ClusterOperatorsNotAvailable(Unable to apply 4.21.0-0.ci-2025-11-05-120652-test-ci-op-hjgxcikk-latest: some cluster operators are not available) eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=True, got ClusterVersionSucceeding=False: ClusterOperatorsNotAvailable(Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available) eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=True, got ClusterVersionAvailable=False: FromClusterVersion hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
33m13.68s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-nvhl6/autoscaling-qzh5b in 2m51.05s util.go:297: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-qzh5b.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:359: Successfully waited for a successful connection to the guest API server in 22.6s eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:541: Failed to wait for 1 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 1 nodes, got 0
TestAzureScheduler
45m57.2s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-x7xk7/azure-scheduler-k4shm in 2m24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-k4shm util.go:2835: Failed to wait for HostedCluster e2e-clusters-x7xk7/azure-scheduler-k4shm to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-x7xk7/azure-scheduler-k4shm invalid at RV 33445 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=True, got ClusterVersionSucceeding=False: ClusterOperatorsNotAvailable(Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available) eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=True, got ClusterVersionAvailable=False: FromClusterVersion eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=False, got ClusterVersionProgressing=True: ClusterOperatorsNotAvailable(Unable to apply 4.21.0-0.ci-2025-11-05-120652-test-ci-op-hjgxcikk-latest: some cluster operators are not available) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
33m9.2s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-x7xk7/azure-scheduler-k4shm in 2m54.125s util.go:297: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-k4shm.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-k4shm.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:359: Successfully waited for a successful connection to the guest API server in 15.025s util.go:541: Failed to wait for 2 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 2 nodes, got 0
TestCreateCluster
46m8.3s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-5nj7v/create-cluster-7r9p2 in 2m41s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-7r9p2 util.go:2835: Failed to wait for HostedCluster e2e-clusters-5nj7v/create-cluster-7r9p2 to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-5nj7v/create-cluster-7r9p2 invalid at RV 33417 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=True, got ClusterVersionSucceeding=False: ClusterOperatorsNotAvailable(Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available) eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=False, got ClusterVersionProgressing=True: ClusterOperatorsNotAvailable(Unable to apply 4.21.0-0.ci-2025-11-05-120652-test-ci-op-hjgxcikk-latest: some cluster operators are not available) eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=True, got ClusterVersionAvailable=False: FromClusterVersion hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
32m52.62s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5nj7v/create-cluster-7r9p2 in 2m39.075s util.go:297: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-7r9p2.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF util.go:359: Successfully waited for a successful connection to the guest API server in 13.5s util.go:541: Failed to wait for 2 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 2 nodes, got 0
TestCreateClusterCustomConfig
45m46.19s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-zzrlj/custom-config-tzlgz in 2m30s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-tzlgz util.go:2835: Failed to wait for HostedCluster e2e-clusters-zzrlj/custom-config-tzlgz to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-zzrlj/custom-config-tzlgz invalid at RV 33312 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=True, got ClusterVersionSucceeding=False: ClusterOperatorsNotAvailable(Cluster operators dns, kube-storage-version-migrator, monitoring, service-ca, storage are not available) eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=False, got ClusterVersionProgressing=True: ClusterOperatorsNotAvailable(Unable to apply 4.21.0-0.ci-2025-11-05-120652-test-ci-op-hjgxcikk-latest: some cluster operators are not available) eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=True, got ClusterVersionAvailable=False: FromClusterVersion hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
33m37.77s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zzrlj/custom-config-tzlgz in 2m45.1s util.go:297: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-tzlgz.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-tzlgz.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-tzlgz.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-tzlgz.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF util.go:359: Successfully waited for a successful connection to the guest API server in 52.625s util.go:541: Failed to wait for 2 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 2 nodes, got 0
TestNodePool
0s
TestNodePool/HostedCluster0
53m56.35s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-59hq4/node-pool-lk4jr in 2m28s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-lk4jr util.go:2835: Successfully waited for HostedCluster e2e-clusters-59hq4/node-pool-lk4jr to have valid conditions in 75ms hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestNodePool/HostedCluster0/Main
160ms
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-59hq4/node-pool-lk4jr in 50ms util.go:297: Successfully waited for kubeconfig secret to have data in 50ms util.go:359: Successfully waited for a successful connection to the guest API server in 25ms
TestNodePool/HostedCluster0/Main/TestMirrorConfigs
30m0.08s
nodepool_mirrorconfigs_test.go:61: Starting test MirrorConfigsTest eventually.go:258: Failed to get **v1.Node: Get "https://api-node-pool-lk4jr.aks-e2e.hypershift.azure.devcluster.openshift.com:443/api/v1/nodes?labelSelector=hypershift.openshift.io%2FnodePool%3Dnode-pool-lk4jr-test-mirrorconfigs": context deadline exceeded util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-59hq4/node-pool-lk4jr-test-mirrorconfigs 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
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigAppliedInPlace
30m0.05s
nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest util.go:541: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-59hq4/node-pool-lk4jr-test-ntomachineconfig-inplace in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 2 nodes, got 0
TestNodePool/HostedCluster0/Main/TestNTOMachineConfigGetsRolledOut
30m0.08s
nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:541: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-59hq4/node-pool-lk4jr-test-ntomachineconfig-replace in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 2 nodes, got 0
TestNodePool/HostedCluster0/Main/TestNTOPerformanceProfile
30m0.08s
nodepool_nto_performanceprofile_test.go:60: Starting test NTOPerformanceProfileTest eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-59hq4/node-pool-lk4jr-test-ntoperformanceprofile 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
TestNodePool/HostedCluster0/Main/TestNodePoolInPlaceUpgrade
30m0.05s
nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-59hq4/node-pool-lk4jr-test-inplaceupgrade 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
TestNodePool/HostedCluster0/Main/TestNodePoolPrevReleaseN1
30m0.08s
nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-59hq4/node-pool-lk4jr-6slmb 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
TestNodePool/HostedCluster0/Main/TestNodePoolPrevReleaseN2
30m0.08s
nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. eventually.go:258: Failed to get **v1.Node: Get "https://api-node-pool-lk4jr.aks-e2e.hypershift.azure.devcluster.openshift.com:443/api/v1/nodes?labelSelector=hypershift.openshift.io%2FnodePool%3Dnode-pool-lk4jr-dvv5b": context deadline exceeded util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-59hq4/node-pool-lk4jr-dvv5b 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
TestNodePool/HostedCluster0/Main/TestNodePoolReplaceUpgrade
30m0.08s
nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-59hq4/node-pool-lk4jr-test-replaceupgrade 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
TestNodePool/HostedCluster0/Main/TestNodepoolMachineconfigGetsRolledout
30m0.05s
nodepool_machineconfig_test.go:55: Starting test NodePoolMachineconfigRolloutTest eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-59hq4/node-pool-lk4jr-test-machineconfig 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
TestNodePool/HostedCluster0/Main/TestRollingUpgrade
30m0.08s
eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:541: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-59hq4/node-pool-lk4jr-test-rolling-upgrade in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1.Node state after 30m0s eventually.go:400: - observed **v1.Node collection invalid: expected 2 nodes, got 0
TestNodePool/HostedCluster2
54m13.63s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-ll45f/node-pool-9qxjv in 2m26s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-9qxjv util.go:2835: Successfully waited for HostedCluster e2e-clusters-ll45f/node-pool-9qxjv to have valid conditions in 75ms hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestNodePool/HostedCluster2/Main
170ms
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ll45f/node-pool-9qxjv in 50ms util.go:297: Successfully waited for kubeconfig secret to have data in 50ms util.go:359: Successfully waited for a successful connection to the guest API server in 50ms
TestNodePool/HostedCluster2/Main/TestAdditionalTrustBundlePropagation
30m0.04s
nodepool_additionalTrustBundlePropagation_test.go:39: Starting AdditionalTrustBundlePropagationTest. eventually.go:258: Failed to get **v1.Node: context deadline exceeded util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-ll45f/node-pool-9qxjv-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
TestUpgradeControlPlane
47m35.74s
control_plane_upgrade_test.go:26: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-hjgxcikk/release@sha256:b710deefddbbc97922b32109c8e18cb97872967e9f82b047f484206c2d70281f, toImage: registry.build01.ci.openshift.org/ci-op-hjgxcikk/release@sha256:446a2b3df5bef3433b0d6c3485ceda90eae319b16ff0bbc3a5179f67c4d85ea9 hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-t6fnj/control-plane-upgrade-cxzs6 in 2m34s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-cxzs6 util.go:2835: Failed to wait for HostedCluster e2e-clusters-t6fnj/control-plane-upgrade-cxzs6 to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-t6fnj/control-plane-upgrade-cxzs6 invalid at RV 34659 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionSucceeding=True, got ClusterVersionSucceeding=False: ClusterOperatorsNotAvailable(Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available) eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=False, got ClusterVersionProgressing=True: ClusterOperatorsNotAvailable(Unable to apply 4.21.0-0.ci-2025-11-05-010554: some cluster operators are not available) eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=True, got ClusterVersionAvailable=False: FromClusterVersion hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestUpgradeControlPlane/ValidateHostedCluster
33m29.34s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-t6fnj/control-plane-upgrade-cxzs6 in 3m6.05s util.go:297: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-control-plane-upgrade-cxzs6.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:359: Successfully waited for a successful connection to the guest API server in 23.25s eventually.go:258: Failed to get **v1.Node: Get "https://api-control-plane-upgrade-cxzs6.aks-e2e.hypershift.azure.devcluster.openshift.com:443/api/v1/nodes": context deadline exceeded util.go:541: Failed to wait for 2 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 2 nodes, got 0