PR #7143 - 11-04 19:32

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

97
Total Tests
46
Passed
26
Failed
25
Skipped

Failed Tests

TestAutoscaling
45m34.39s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-68bbf/autoscaling-bpbql in 2m43s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-bpbql util.go:2835: Failed to wait for HostedCluster e2e-clusters-68bbf/autoscaling-bpbql to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-68bbf/autoscaling-bpbql invalid at RV 34280 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-04-195457-test-ci-op-ht9znpsm-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
TestAutoscaling/ValidateHostedCluster
33m1.37s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-68bbf/autoscaling-bpbql in 2m42.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-bpbql.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 19.275s 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
45m44.26s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-vsjvj/azure-scheduler-66nml in 2m15s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-66nml util.go:2835: Failed to wait for HostedCluster e2e-clusters-vsjvj/azure-scheduler-66nml to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-vsjvj/azure-scheduler-66nml invalid at RV 34325 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-04-195457-test-ci-op-ht9znpsm-latest: some cluster operators are not available) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
33m28.46s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vsjvj/azure-scheduler-66nml 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-azure-scheduler-66nml.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-azure-scheduler-66nml.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 28.375s 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
TestCreateCluster
46m56.17s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-zp9zj/create-cluster-4t7c6 in 2m34s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-4t7c6 util.go:2835: Failed to wait for HostedCluster e2e-clusters-zp9zj/create-cluster-4t7c6 to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-zp9zj/create-cluster-4t7c6 invalid at RV 34149 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionProgressing=False, got ClusterVersionProgressing=True: ClusterOperatorsNotAvailable(Unable to apply 4.21.0-0.ci-2025-11-04-195457-test-ci-op-ht9znpsm-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
TestCreateCluster/ValidateHostedCluster
33m10.56s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zp9zj/create-cluster-4t7c6 in 2m48.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-4t7c6.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-create-cluster-4t7c6.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.45s eventually.go:258: Failed to get **v1.Node: Get "https://api-create-cluster-4t7c6.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
TestCreateClusterCustomConfig
45m45.82s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-2nt2j/custom-config-njj7v in 2m33s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-njj7v util.go:2835: Failed to wait for HostedCluster e2e-clusters-2nt2j/custom-config-njj7v to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-2nt2j/custom-config-njj7v invalid at RV 33828 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-04-195457-test-ci-op-ht9znpsm-latest: some cluster operators are not available) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
33m32.5s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2nt2j/custom-config-njj7v 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-custom-config-njj7v.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.425s 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
TestNodePool
0s
TestNodePool/HostedCluster0
53m59.39s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-w4g89/node-pool-6jc79 in 2m13s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-6jc79 util.go:2835: Successfully waited for HostedCluster e2e-clusters-w4g89/node-pool-6jc79 to have valid conditions in 75ms hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestNodePool/HostedCluster0/Main
550ms
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-w4g89/node-pool-6jc79 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 425ms
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-w4g89/node-pool-6jc79-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.04s
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-w4g89/node-pool-6jc79-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.04s
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-w4g89/node-pool-6jc79-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-w4g89/node-pool-6jc79-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.04s
nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-w4g89/node-pool-6jc79-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.05s
nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-w4g89/node-pool-6jc79-l9mmf 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: context deadline exceeded util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-w4g89/node-pool-6jc79-8hbxq 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.04s
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-w4g89/node-pool-6jc79-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-w4g89/node-pool-6jc79-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
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-w4g89/node-pool-6jc79-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
53m39.86s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-wvmqm/node-pool-xgxnx in 2m36s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-xgxnx util.go:2835: Successfully waited for HostedCluster e2e-clusters-wvmqm/node-pool-xgxnx to have valid conditions in 50ms 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-wvmqm/node-pool-xgxnx 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-wvmqm/node-pool-xgxnx-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
48m6.43s
control_plane_upgrade_test.go:26: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-ht9znpsm/release@sha256:45f373ca100ac2702dfa8bc055c8feff24ade29c339cfe13ac06ab21daec75b1, toImage: registry.build01.ci.openshift.org/ci-op-ht9znpsm/release@sha256:c3f247023f2bf0044a43afa6f02828c2643f33210d9a1b95267147b9b35d43a0 hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-rwzrm/control-plane-upgrade-sg82n in 2m17s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-sg82n util.go:2835: Failed to wait for HostedCluster e2e-clusters-rwzrm/control-plane-upgrade-sg82n to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-rwzrm/control-plane-upgrade-sg82n invalid at RV 31525 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-04-112427: 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
34m29.97s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-rwzrm/control-plane-upgrade-sg82n in 3m51.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-sg82n.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-sg82n.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-sg82n.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-sg82n.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-sg82n.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.875s 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