PR #7137 - 11-06 15:29

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

98
Total Tests
46
Passed
26
Failed
26
Skipped

Failed Tests

TestAutoscaling
46m15.77s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-k2gc5/autoscaling-gfx9k in 2m16s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-gfx9k util.go:2835: Failed to wait for HostedCluster e2e-clusters-k2gc5/autoscaling-gfx9k to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-k2gc5/autoscaling-gfx9k invalid at RV 34577 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-06-154825-test-ci-op-kqc2g4qt-latest: some cluster operators are not available) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
33m13.34s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k2gc5/autoscaling-gfx9k in 3m0.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-gfx9k.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-autoscaling-gfx9k.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 13.25s 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
46m3.29s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-8q5ds/azure-scheduler-5zjwh in 2m22s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-5zjwh util.go:2835: Failed to wait for HostedCluster e2e-clusters-8q5ds/azure-scheduler-5zjwh to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-8q5ds/azure-scheduler-5zjwh invalid at RV 34654 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-06-154825-test-ci-op-kqc2g4qt-latest: some cluster operators are not available) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
32m53.35s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8q5ds/azure-scheduler-5zjwh in 2m39.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-azure-scheduler-5zjwh.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 14.25s 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
46m16.72s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-5qgnq/create-cluster-w7ptf in 2m7s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-w7ptf util.go:2835: Failed to wait for HostedCluster e2e-clusters-5qgnq/create-cluster-w7ptf to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-5qgnq/create-cluster-w7ptf invalid at RV 34658 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-06-154825-test-ci-op-kqc2g4qt-latest: some cluster operators are not available) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
33m17.38s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5qgnq/create-cluster-w7ptf in 2m36.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-create-cluster-w7ptf.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 41.3s eventually.go:258: Failed to get **v1.Node: 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
TestCreateClusterCustomConfig
45m35.29s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-wpx4k/custom-config-f45qr in 2m18s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-f45qr util.go:2835: Failed to wait for HostedCluster e2e-clusters-wpx4k/custom-config-f45qr to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-wpx4k/custom-config-f45qr invalid at RV 34496 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 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-06-154825-test-ci-op-kqc2g4qt-latest: some cluster operators are not available) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
33m14.54s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wpx4k/custom-config-f45qr in 2m36.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-custom-config-f45qr.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-f45qr.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 38.45s 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
53m59.76s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-xbqqc/node-pool-jf9s7 in 2m24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-jf9s7 util.go:2835: Successfully waited for HostedCluster e2e-clusters-xbqqc/node-pool-jf9s7 to have valid conditions in 75ms hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestNodePool/HostedCluster0/Main
170ms
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-xbqqc/node-pool-jf9s7 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/HostedCluster0/Main/TestMirrorConfigs
30m0.08s
nodepool_mirrorconfigs_test.go:61: Starting test MirrorConfigsTest util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-xbqqc/node-pool-jf9s7-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.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-xbqqc/node-pool-jf9s7-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 util.go:541: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-xbqqc/node-pool-jf9s7-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.05s
nodepool_nto_performanceprofile_test.go:60: Starting test NTOPerformanceProfileTest util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-xbqqc/node-pool-jf9s7-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.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-xbqqc/node-pool-jf9s7-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.07s
nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-xbqqc/node-pool-jf9s7-4vtsx 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.07s
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-xbqqc/node-pool-jf9s7-6kmrq 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.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-xbqqc/node-pool-jf9s7-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.08s
nodepool_machineconfig_test.go:55: Starting test NodePoolMachineconfigRolloutTest util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-xbqqc/node-pool-jf9s7-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.05s
util.go:541: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-xbqqc/node-pool-jf9s7-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
54m22.22s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-d59kb/node-pool-7xq66 in 2m22s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-7xq66 util.go:2835: Successfully waited for HostedCluster e2e-clusters-d59kb/node-pool-7xq66 to have valid conditions in 100ms hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestNodePool/HostedCluster2/Main
530ms
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-d59kb/node-pool-7xq66 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 400ms
TestNodePool/HostedCluster2/Main/TestAdditionalTrustBundlePropagation
30m0.05s
nodepool_additionalTrustBundlePropagation_test.go:39: Starting AdditionalTrustBundlePropagationTest. util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-d59kb/node-pool-7xq66-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
48m13.23s
control_plane_upgrade_test.go:26: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-kqc2g4qt/release@sha256:806106e231f7ef70bf59e02d318b05f90c79ea53c2d3425560845b64e61b03a0, toImage: registry.build01.ci.openshift.org/ci-op-kqc2g4qt/release@sha256:400887cfad24a1bb1469ffba51ad950a06dc3fe26eec6ac63e3c4a9136de06e6 hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-t9lvk/control-plane-upgrade-99w4b in 2m16s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-99w4b util.go:2835: Failed to wait for HostedCluster e2e-clusters-t9lvk/control-plane-upgrade-99w4b to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-t9lvk/control-plane-upgrade-99w4b invalid at RV 46371 after 2s: eventually.go:227: - incorrect condition: wanted Available=True, got Available=False: KASLoadBalancerNotReachable(Get "https://api-control-plane-upgrade-99w4b.aks-e2e.hypershift.azure.devcluster.openshift.com:443/healthz": dial tcp: lookup api-control-plane-upgrade-99w4b.aks-e2e.hypershift.azure.devcluster.openshift.com on 10.0.0.10:53: no such host) eventually.go:227: - incorrect condition: wanted ExternalDNSReachable=True, got ExternalDNSReachable=False: ExternalDNSHostNotReachable(lookup api-control-plane-upgrade-99w4b.aks-e2e.hypershift.azure.devcluster.openshift.com on 10.0.0.10:53: no such host) 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-06-012216: 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) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestUpgradeControlPlane/ValidateHostedCluster
34m39.88s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-t9lvk/control-plane-upgrade-99w4b in 4m6.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-99w4b.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-control-plane-upgrade-99w4b.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-control-plane-upgrade-99w4b.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 33.8s eventually.go:258: Failed to get **v1.Node: 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