PR #7061 - 11-05 17:12

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

131
Total Tests
80
Passed
24
Failed
27
Skipped

Failed Tests

TestAutoscaling
46m3.46s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-g9j87/autoscaling-9xvpx in 2m24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-9xvpx util.go:2835: Failed to wait for HostedCluster e2e-clusters-g9j87/autoscaling-9xvpx to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-g9j87/autoscaling-9xvpx invalid at RV 33517 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-174005-test-ci-op-szf1j0hk-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
33m17.34s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-g9j87/autoscaling-9xvpx in 3m0.05s util.go:297: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-9xvpx.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 17.275s 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
46m24.63s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-qbzgp/azure-scheduler-8k5nk in 2m31s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-8k5nk util.go:2835: Failed to wait for HostedCluster e2e-clusters-qbzgp/azure-scheduler-8k5nk to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-qbzgp/azure-scheduler-8k5nk invalid at RV 33725 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-174005-test-ci-op-szf1j0hk-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
TestAzureScheduler/ValidateHostedCluster
33m32.88s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qbzgp/azure-scheduler-8k5nk in 3m18.05s util.go:297: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-8k5nk.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 14.8s 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
46m34.31s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-79d8l/create-cluster-pdfkc in 2m9s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-pdfkc util.go:2835: Failed to wait for HostedCluster e2e-clusters-79d8l/create-cluster-pdfkc to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-79d8l/create-cluster-pdfkc invalid at RV 33718 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-174005-test-ci-op-szf1j0hk-latest: some cluster operators are not available) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
33m47.5s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-79d8l/create-cluster-pdfkc in 3m27.05s util.go:297: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-pdfkc.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-pdfkc.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 20.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
TestCreateClusterCustomConfig
45m52.68s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-6gs8b/custom-config-kgfjd in 2m24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-kgfjd util.go:2835: Failed to wait for HostedCluster e2e-clusters-6gs8b/custom-config-kgfjd to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-6gs8b/custom-config-kgfjd invalid at RV 33598 after 2s: eventually.go:227: - incorrect condition: wanted ClusterVersionAvailable=True, got ClusterVersionAvailable=False: FromClusterVersion 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-174005-test-ci-op-szf1j0hk-latest: some cluster operators are not available) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
33m32.62s
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-6gs8b/custom-config-kgfjd in 2m45.05s util.go:297: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-kgfjd.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-kgfjd.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 47.525s 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
54m19.46s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-j4bnn/node-pool-47tlm in 2m40s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-47tlm util.go:2835: Successfully waited for HostedCluster e2e-clusters-j4bnn/node-pool-47tlm 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-j4bnn/node-pool-47tlm in 50ms util.go:297: Successfully waited for kubeconfig secret to have data in 25ms util.go:359: Successfully waited for a successful connection to the guest API server in 25ms
TestNodePool/HostedCluster0/Main/TestMirrorConfigs
30m0.04s
nodepool_mirrorconfigs_test.go:61: Starting test MirrorConfigsTest 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-j4bnn/node-pool-47tlm-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.07s
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-j4bnn/node-pool-47tlm-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.07s
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-j4bnn/node-pool-47tlm-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 util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-j4bnn/node-pool-47tlm-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.06s
nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-j4bnn/node-pool-47tlm-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-j4bnn/node-pool-47tlm-twxv9 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.06s
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-j4bnn/node-pool-47tlm-5r9sd 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 util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-j4bnn/node-pool-47tlm-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.06s
nodepool_machineconfig_test.go:55: Starting test NodePoolMachineconfigRolloutTest util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-j4bnn/node-pool-47tlm-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-j4bnn/node-pool-47tlm-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
54m34.58s
hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-v8chl/node-pool-smw69 in 2m43s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-smw69 util.go:2835: Successfully waited for HostedCluster e2e-clusters-v8chl/node-pool-smw69 to have valid conditions in 75ms hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called
TestNodePool/HostedCluster2/Main
340ms
util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-v8chl/node-pool-smw69 in 50ms util.go:297: Successfully waited for kubeconfig secret to have data in 175ms util.go:359: Successfully waited for a successful connection to the guest API server in 25ms
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-v8chl/node-pool-smw69-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