PR #6025 - 11-05 18:35

util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-clpw5/autoscaling-drms4 in 2m57.175s util.go:297: Successfully waited for kubeconfig secret to have data in 100ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-drms4.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-autoscaling-drms4.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-drms4.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 37.35s 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

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-b4j8t/azure-scheduler-98bl7 in 2m11s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-98bl7 util.go:2835: Failed to wait for HostedCluster e2e-clusters-b4j8t/azure-scheduler-98bl7 to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-b4j8t/azure-scheduler-98bl7 invalid at RV 33576 after 2s: 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-191400-test-ci-op-dvc5zw91-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) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called

util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b4j8t/azure-scheduler-98bl7 in 3m21.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-98bl7.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.2s 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

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-rq6tn/create-cluster-rmswp in 2m22s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-rmswp util.go:2835: Failed to wait for HostedCluster e2e-clusters-rq6tn/create-cluster-rmswp to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-rq6tn/create-cluster-rmswp invalid at RV 33448 after 2s: 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-191400-test-ci-op-dvc5zw91-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) hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called

util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-rq6tn/create-cluster-rmswp in 2m57.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-rmswp.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-rmswp.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.275s 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

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-9vw7g/custom-config-k9jnp in 2m12s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-k9jnp util.go:2835: Failed to wait for HostedCluster e2e-clusters-9vw7g/custom-config-k9jnp to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-9vw7g/custom-config-k9jnp invalid at RV 33554 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-191400-test-ci-op-dvc5zw91-latest: some cluster operators are not available) 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 hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called

util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9vw7g/custom-config-k9jnp in 2m57.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-k9jnp.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 42.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

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-9zfjh/node-pool-dkk5f in 2m23s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-dkk5f util.go:2835: Successfully waited for HostedCluster e2e-clusters-9zfjh/node-pool-dkk5f to have valid conditions in 75ms hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called

util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9zfjh/node-pool-dkk5f 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

nodepool_mirrorconfigs_test.go:61: Starting test MirrorConfigsTest util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-9zfjh/node-pool-dkk5f-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

nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest eventually.go:258: Failed to get **v1.Node: Get "https://api-node-pool-dkk5f.aks-e2e.hypershift.azure.devcluster.openshift.com:443/api/v1/nodes?labelSelector=hypershift.openshift.io%2FnodePool%3Dnode-pool-dkk5f-test-ntomachineconfig-inplace": context deadline exceeded util.go:541: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-9zfjh/node-pool-dkk5f-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

nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest eventually.go:258: Failed to get **v1.Node: Get "https://api-node-pool-dkk5f.aks-e2e.hypershift.azure.devcluster.openshift.com:443/api/v1/nodes?labelSelector=hypershift.openshift.io%2FnodePool%3Dnode-pool-dkk5f-test-ntomachineconfig-replace": context deadline exceeded util.go:541: Failed to wait for 2 nodes to become ready for NodePool e2e-clusters-9zfjh/node-pool-dkk5f-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

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-9zfjh/node-pool-dkk5f-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

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-9zfjh/node-pool-dkk5f-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

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-9zfjh/node-pool-dkk5f-8jwzp 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

nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-9zfjh/node-pool-dkk5f-75n8g 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

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-9zfjh/node-pool-dkk5f-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

nodepool_machineconfig_test.go:55: Starting test NodePoolMachineconfigRolloutTest util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-9zfjh/node-pool-dkk5f-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

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-9zfjh/node-pool-dkk5f-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

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-r9rgt/node-pool-sjqvl in 2m11s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-sjqvl util.go:2835: Successfully waited for HostedCluster e2e-clusters-r9rgt/node-pool-sjqvl to have valid conditions in 75ms hypershift_framework.go:242: skipping postTeardown() hypershift_framework.go:223: skipping teardown, already called

util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-r9rgt/node-pool-sjqvl 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 250ms

nodepool_additionalTrustBundlePropagation_test.go:39: Starting AdditionalTrustBundlePropagationTest. eventually.go:258: Failed to get **v1.Node: Get "https://api-node-pool-sjqvl.aks-e2e.hypershift.azure.devcluster.openshift.com:443/api/v1/nodes?labelSelector=hypershift.openshift.io%2FnodePool%3Dnode-pool-sjqvl-test-additional-trust-bundle-propagation": context deadline exceeded util.go:541: Failed to wait for 1 nodes to become ready for NodePool e2e-clusters-r9rgt/node-pool-sjqvl-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

control_plane_upgrade_test.go:26: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-dvc5zw91/release@sha256:a937442bdca84ad7fe05c6d85716665279a1b3d20603c10e381ecc8b00d80192, toImage: registry.build01.ci.openshift.org/ci-op-dvc5zw91/release@sha256:d26b8d49e0151de161732b837ad50227a13d1b2f5e87e59dc728e86a5bf7d71f hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-dxbfw/control-plane-upgrade-7lscq in 2m10s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-7lscq util.go:2835: Failed to wait for HostedCluster e2e-clusters-dxbfw/control-plane-upgrade-7lscq to have valid conditions in 2s: context deadline exceeded eventually.go:224: observed *v1beta1.HostedCluster e2e-clusters-dxbfw/control-plane-upgrade-7lscq invalid at RV 36142 after 2s: 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-130554: 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

util.go:280: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-dxbfw/control-plane-upgrade-7lscq 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-7lscq.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-7lscq.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-7lscq.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 45.15s 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