PR #6965 - 11-10 18:15

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-k48qb/autoscaling-s7gdt in 2m26s util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt in 2m39.075s util.go:298: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-s7gdt.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:360: Successfully waited for a successful connection to the guest API server in 24.35s util.go:542: Successfully waited for 1 nodes to become ready in 8m48.05s util.go:575: Successfully waited for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt to rollout in 7m51.075s util.go:2836: Successfully waited for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt to have valid conditions in 50ms util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-k48qb/autoscaling-s7gdt in 200ms util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:3971: Successfully validated configuration authentication status consistency across HCP, HC, and guest cluster util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 50ms util.go:542: Successfully waited for 1 nodes to become ready in 75ms autoscaling_test.go:107: Enabled autoscaling. Namespace: e2e-clusters-k48qb, name: autoscaling-s7gdt, min: 1, max: 3 autoscaling_test.go:126: Created workload. Node: autoscaling-s7gdt-xb6nd-zlbd8, memcapacity: 15221260Ki util.go:542: Successfully waited for 3 nodes to become ready in 7m51.6s autoscaling_test.go:146: Deleted workload

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 50ms util.go:542: Successfully waited for 1 nodes to become ready in 75ms autoscaling_test.go:107: Enabled autoscaling. Namespace: e2e-clusters-k48qb, name: autoscaling-s7gdt, min: 1, max: 3 autoscaling_test.go:126: Created workload. Node: autoscaling-s7gdt-xb6nd-zlbd8, memcapacity: 15221260Ki util.go:542: Successfully waited for 3 nodes to become ready in 7m51.6s autoscaling_test.go:146: Deleted workload

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt in 2m39.075s util.go:298: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-s7gdt.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:360: Successfully waited for a successful connection to the guest API server in 24.35s util.go:542: Successfully waited for 1 nodes to become ready in 8m48.05s util.go:575: Successfully waited for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt to rollout in 7m51.075s util.go:2836: Successfully waited for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt to have valid conditions in 50ms

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-k48qb/autoscaling-s7gdt in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms

util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-k48qb/autoscaling-s7gdt in 200ms

util.go:3971: Successfully validated configuration authentication status consistency across HCP, HC, and guest cluster

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-wx6vw/azure-scheduler-2plch in 2m24s util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 3m0.05s util.go:298: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-2plch.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-2plch.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF util.go:360: Successfully waited for a successful connection to the guest API server in 15.35s util.go:542: Successfully waited for 2 nodes to become ready in 8m54.1s util.go:575: Successfully waited for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch to rollout in 3m21.05s util.go:2836: Successfully waited for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch to have valid conditions in 50ms util.go:542: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-wx6vw/azure-scheduler-2plch in 175ms util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 125ms util.go:298: Successfully waited for kubeconfig secret to have data in 75ms util.go:3971: Successfully validated configuration authentication status consistency across HCP, HC, and guest cluster util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 50ms util.go:542: Successfully waited for 2 nodes to become ready in 75ms azure_scheduler_test.go:111: Updated clusterSizingConfig. azure_scheduler_test.go:158: Successfully waited for HostedCluster size label and annotations updated in 50ms azure_scheduler_test.go:150: Scaled Nodepool. Namespace: e2e-clusters-wx6vw, name: azure-scheduler-2plch, replicas: 0xc002f57860 util.go:542: Successfully waited for 3 nodes to become ready in 8m6.1s azure_scheduler_test.go:158: Successfully waited for HostedCluster size label and annotations updated in 75ms azure_scheduler_test.go:182: Successfully waited for control-plane-operator pod is running with expected resource request in 50ms util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 50ms util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 50ms util.go:2836: Successfully waited for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch to have valid conditions in 50ms util.go:3111: Successfully waited for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch to have valid Status.Payload in 75ms util.go:1110: test only supported on AWS platform, saw Azure util.go:2419: Checking that all ValidatingAdmissionPolicies are present util.go:2445: Checking Denied KAS Requests for ValidatingAdmissionPolicies util.go:2461: Checking ClusterOperator status modifications are allowed util.go:3798: All 45 pods in namespace e2e-clusters-wx6vw-azure-scheduler-2plch have the expected RunAsUser UID 1007

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 50ms util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 50ms util.go:2836: Successfully waited for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch to have valid conditions in 50ms

util.go:1110: test only supported on AWS platform, saw Azure

util.go:3111: Successfully waited for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch to have valid Status.Payload in 75ms

util.go:3798: All 45 pods in namespace e2e-clusters-wx6vw-azure-scheduler-2plch have the expected RunAsUser UID 1007

util.go:2445: Checking Denied KAS Requests for ValidatingAdmissionPolicies

util.go:2461: Checking ClusterOperator status modifications are allowed

util.go:2419: Checking that all ValidatingAdmissionPolicies are present

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 50ms util.go:542: Successfully waited for 2 nodes to become ready in 75ms azure_scheduler_test.go:111: Updated clusterSizingConfig. azure_scheduler_test.go:158: Successfully waited for HostedCluster size label and annotations updated in 50ms azure_scheduler_test.go:150: Scaled Nodepool. Namespace: e2e-clusters-wx6vw, name: azure-scheduler-2plch, replicas: 0xc002f57860 util.go:542: Successfully waited for 3 nodes to become ready in 8m6.1s azure_scheduler_test.go:158: Successfully waited for HostedCluster size label and annotations updated in 75ms azure_scheduler_test.go:182: Successfully waited for control-plane-operator pod is running with expected resource request in 50ms

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 3m0.05s util.go:298: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-2plch.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-2plch.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF util.go:360: Successfully waited for a successful connection to the guest API server in 15.35s util.go:542: Successfully waited for 2 nodes to become ready in 8m54.1s util.go:575: Successfully waited for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch to rollout in 3m21.05s util.go:2836: Successfully waited for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch to have valid conditions in 50ms

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wx6vw/azure-scheduler-2plch in 125ms util.go:298: Successfully waited for kubeconfig secret to have data in 75ms

util.go:542: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-wx6vw/azure-scheduler-2plch in 175ms

util.go:3971: Successfully validated configuration authentication status consistency across HCP, HC, and guest cluster

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-7fslx/create-cluster-p5qh9 in 2m14s hypershift_framework.go:484: Destroyed cluster. Namespace: e2e-clusters-7fslx, name: create-cluster-p5qh9 hypershift_framework.go:439: archiving /logs/artifacts/TestCreateCluster/hostedcluster-create-cluster-p5qh9 to /logs/artifacts/TestCreateCluster/hostedcluster.tar.gz util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7fslx/create-cluster-p5qh9 in 2m45.05s util.go:298: Successfully waited for kubeconfig secret to have data in 75ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-p5qh9.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-p5qh9.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-create-cluster-p5qh9.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF util.go:360: Successfully waited for a successful connection to the guest API server in 28.5s util.go:542: Successfully waited for 2 nodes to become ready in 9m33.075s util.go:575: Successfully waited for HostedCluster e2e-clusters-7fslx/create-cluster-p5qh9 to rollout in 3m57.075s util.go:2836: Successfully waited for HostedCluster e2e-clusters-7fslx/create-cluster-p5qh9 to have valid conditions in 50ms

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7fslx/create-cluster-p5qh9 in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 25ms create_cluster_test.go:2225: fetching mgmt kubeconfig util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7fslx/create-cluster-p5qh9 in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms

util.go:4036: No Pods found for PodMonitor e2e-clusters-7fslx-create-cluster-p5qh9/cluster-autoscaler, skipping

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-cl6qt/node-pool-bqz57 in 2m15s nodepool_test.go:143: tests only supported on platform KubeVirt hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-qxmzd/node-pool-wjpzh in 2m23s util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cl6qt/node-pool-bqz57 in 2m57.05s util.go:298: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-bqz57.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:360: Successfully waited for a successful connection to the guest API server in 17.25s util.go:542: Successfully waited for 0 nodes to become ready in 75ms util.go:2836: Successfully waited for HostedCluster e2e-clusters-cl6qt/node-pool-bqz57 to have valid conditions in 8m12.05s util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qxmzd/node-pool-wjpzh in 2m57.075s util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 8.375s util.go:542: Successfully waited for 0 nodes to become ready in 75ms util.go:2836: Successfully waited for HostedCluster e2e-clusters-qxmzd/node-pool-wjpzh to have valid conditions in 8m21.075s util.go:542: Successfully waited for 0 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57 in 125ms util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cl6qt/node-pool-bqz57 in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:3971: Successfully validated configuration authentication status consistency across HCP, HC, and guest cluster util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cl6qt/node-pool-bqz57 in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 25ms nodepool_kms_root_volume_test.go:40: test only supported on platform AWS nodepool_autorepair_test.go:43: test only supported on platform AWS nodepool_machineconfig_test.go:55: Starting test NodePoolMachineconfigRolloutTest util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-machineconfig in 12m36.1s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-machineconfig to have correct status in 50ms util.go:456: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-machineconfig to start config update in 50ms nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest util.go:542: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-replace in 19m12.125s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-replace to have correct status in 50ms util.go:456: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-replace to start config update in 15.05s nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest util.go:542: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-inplace in 12m39.05s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-inplace to have correct status in 50ms util.go:456: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-inplace to start config update in 15.05s nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-replaceupgrade in 7m45.025s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-replaceupgrade to have correct status in 50ms nodepool_upgrade_test.go:160: Validating all Nodes have the synced labels and taints nodepool_upgrade_test.go:163: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-replaceupgrade to have version 4.21.0-0.ci-2025-11-10-035626 in 50ms nodepool_upgrade_test.go:180: Updating NodePool image. Image: registry.build01.ci.openshift.org/ci-op-tjjzqxdw/release@sha256:a6ad9f64729aae6bf95775829ffb3225efc658c7c49411bb3ae4f0ac13547be4 nodepool_upgrade_test.go:187: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-replaceupgrade to start the upgrade in 3.05s nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade in 12m48.05s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade to have correct status in 50ms nodepool_upgrade_test.go:160: Validating all Nodes have the synced labels and taints nodepool_upgrade_test.go:163: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade to have version 4.21.0-0.ci-2025-11-10-035626 in 50ms nodepool_upgrade_test.go:180: Updating NodePool image. Image: registry.build01.ci.openshift.org/ci-op-tjjzqxdw/release@sha256:a6ad9f64729aae6bf95775829ffb3225efc658c7c49411bb3ae4f0ac13547be4 nodepool_upgrade_test.go:187: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade to start the upgrade in 3.05s nodepool_upgrade_test.go:200: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade to have version 4.21.0-0.ci-2025-11-10-183549-test-ci-op-tjjzqxdw-latest in 6m57.05s util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade in 9.075s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade to have correct status in 50ms nodepool_kv_cache_image_test.go:43: test only supported on platform KubeVirt util.go:542: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-rolling-upgrade in 19m27.05s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-rolling-upgrade to have correct status in 3.05s nodepool_rolling_upgrade_test.go:89: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-rolling-upgrade to start the rolling upgrade in 3.05s nodepool_day2_tags_test.go:44: test only supported on platform AWS nodepool_kv_qos_guaranteed_test.go:44: test only supported on platform KubeVirt nodepool_kv_jsonpatch_test.go:43: test only supported on platform KubeVirt nodepool_kv_nodeselector_test.go:49: test only supported on platform KubeVirt nodepool_kv_multinet_test.go:37: test only supported on platform KubeVirt nodepool_osp_advanced_test.go:54: Starting test OpenStackAdvancedTest nodepool_osp_advanced_test.go:57: test only supported on platform OpenStack nodepool_nto_performanceprofile_test.go:60: Starting test NTOPerformanceProfileTest util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntoperformanceprofile in 15m12.075s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntoperformanceprofile to have correct status in 50ms nodepool_nto_performanceprofile_test.go:81: Entering NTO PerformanceProfile test nodepool_nto_performanceprofile_test.go:111: Hosted control plane namespace is e2e-clusters-cl6qt-node-pool-bqz57 nodepool_nto_performanceprofile_test.go:113: Successfully waited for performance profile ConfigMap to exist with correct name labels and annotations in 3.05s nodepool_nto_performanceprofile_test.go:160: Successfully waited for performance profile status ConfigMap to exist in 50ms nodepool_nto_performanceprofile_test.go:202: Successfully waited for performance profile status to be reflected under the NodePool status in 50ms nodepool_nto_performanceprofile_test.go:255: Deleting configmap reference from nodepool ... nodepool_nto_performanceprofile_test.go:262: Successfully waited for performance profile ConfigMap to be deleted in 3.05s nodepool_nto_performanceprofile_test.go:281: Ending NTO PerformanceProfile test: OK nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntoperformanceprofile to have correct status in 50ms nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-5xxnt in 9m42.075s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-5xxnt to have correct status in 3.05s nodepool_prev_release_test.go:55: NodePoolPrevReleaseCreateTest tests the creation of a NodePool with previous OCP release. nodepool_prev_release_test.go:57: Validating all Nodes have the synced labels and taints nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-5xxnt to have correct status in 50ms nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-fs6nf in 15m12.05s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-fs6nf to have correct status in 50ms nodepool_prev_release_test.go:55: NodePoolPrevReleaseCreateTest tests the creation of a NodePool with previous OCP release. nodepool_prev_release_test.go:57: Validating all Nodes have the synced labels and taints nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-fs6nf to have correct status in 50ms nodepool_mirrorconfigs_test.go:61: Starting test MirrorConfigsTest util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-mirrorconfigs in 19m0.075s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-mirrorconfigs to have correct status in 50ms nodepool_mirrorconfigs_test.go:82: Entering MirrorConfigs test nodepool_mirrorconfigs_test.go:112: Hosted control plane namespace is e2e-clusters-cl6qt-node-pool-bqz57 nodepool_mirrorconfigs_test.go:114: Successfully waited for kubeletConfig should be mirrored and present in the hosted cluster in 3.025s nodepool_mirrorconfigs_test.go:158: Deleting KubeletConfig configmap reference from nodepool ... nodepool_mirrorconfigs_test.go:164: Successfully waited for KubeletConfig configmap to be deleted in 3.05s nodepool_mirrorconfigs_test.go:102: Exiting MirrorConfigs test: OK nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-mirrorconfigs to have correct status in 75ms nodepool_imagetype_test.go:46: test is only supported for AWS platform util.go:542: Successfully waited for 0 nodes to become ready for NodePool e2e-clusters-qxmzd/node-pool-wjpzh in 125ms util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qxmzd/node-pool-wjpzh in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:3971: Successfully validated configuration authentication status consistency across HCP, HC, and guest cluster util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qxmzd/node-pool-wjpzh in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 25ms nodepool_additionalTrustBundlePropagation_test.go:39: Starting AdditionalTrustBundlePropagationTest. util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-qxmzd/node-pool-wjpzh-test-additional-trust-bundle-propagation in 5m39.05s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-qxmzd/node-pool-wjpzh-test-additional-trust-bundle-propagation to have correct status in 50ms nodepool_additionalTrustBundlePropagation_test.go:73: Updating hosted cluster with additional trust bundle. Bundle: additional-trust-bundle nodepool_additionalTrustBundlePropagation_test.go:81: Successfully waited for Waiting for NodePool e2e-clusters-qxmzd/node-pool-wjpzh-test-additional-trust-bundle-propagation to begin updating in 10.05s nodepool_additionalTrustBundlePropagation_test.go:95: Successfully waited for Waiting for NodePool e2e-clusters-qxmzd/node-pool-wjpzh-test-additional-trust-bundle-propagation to stop updating in 11m20.05s nodepool_additionalTrustBundlePropagation_test.go:113: Updating hosted cluster by removing additional trust bundle. nodepool_additionalTrustBundlePropagation_test.go:127: Successfully waited for Waiting for control plane operator deployment to be updated in 75ms nodepool_additionalTrustBundlePropagation_test.go:148: Successfully waited for Waiting for NodePool e2e-clusters-qxmzd/node-pool-wjpzh-test-additional-trust-bundle-propagation to begin updating in 10.05s

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-cl6qt/node-pool-bqz57 in 2m15s

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cl6qt/node-pool-bqz57 in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 25ms

nodepool_kv_jsonpatch_test.go:43: test only supported on platform KubeVirt

nodepool_kv_multinet_test.go:37: test only supported on platform KubeVirt

nodepool_kv_nodeselector_test.go:49: test only supported on platform KubeVirt

nodepool_kv_qos_guaranteed_test.go:44: test only supported on platform KubeVirt

nodepool_osp_advanced_test.go:54: Starting test OpenStackAdvancedTest nodepool_osp_advanced_test.go:57: test only supported on platform OpenStack

nodepool_imagetype_test.go:46: test is only supported for AWS platform

nodepool_kms_root_volume_test.go:40: test only supported on platform AWS

nodepool_mirrorconfigs_test.go:61: Starting test MirrorConfigsTest util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-mirrorconfigs in 19m0.075s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-mirrorconfigs to have correct status in 50ms nodepool_mirrorconfigs_test.go:82: Entering MirrorConfigs test nodepool_mirrorconfigs_test.go:112: Hosted control plane namespace is e2e-clusters-cl6qt-node-pool-bqz57 nodepool_mirrorconfigs_test.go:114: Successfully waited for kubeletConfig should be mirrored and present in the hosted cluster in 3.025s nodepool_mirrorconfigs_test.go:158: Deleting KubeletConfig configmap reference from nodepool ... nodepool_mirrorconfigs_test.go:164: Successfully waited for KubeletConfig configmap to be deleted in 3.05s nodepool_mirrorconfigs_test.go:102: Exiting MirrorConfigs test: OK nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-mirrorconfigs to have correct status in 75ms

nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest util.go:542: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-inplace in 12m39.05s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-inplace to have correct status in 50ms util.go:456: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-inplace to start config update in 15.05s

nodepool_nto_machineconfig_test.go:68: Starting test NTOMachineConfigRolloutTest util.go:542: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-replace in 19m12.125s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-replace to have correct status in 50ms util.go:456: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntomachineconfig-replace to start config update in 15.05s

nodepool_nto_performanceprofile_test.go:60: Starting test NTOPerformanceProfileTest util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntoperformanceprofile in 15m12.075s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntoperformanceprofile to have correct status in 50ms nodepool_nto_performanceprofile_test.go:81: Entering NTO PerformanceProfile test nodepool_nto_performanceprofile_test.go:111: Hosted control plane namespace is e2e-clusters-cl6qt-node-pool-bqz57 nodepool_nto_performanceprofile_test.go:113: Successfully waited for performance profile ConfigMap to exist with correct name labels and annotations in 3.05s nodepool_nto_performanceprofile_test.go:160: Successfully waited for performance profile status ConfigMap to exist in 50ms nodepool_nto_performanceprofile_test.go:202: Successfully waited for performance profile status to be reflected under the NodePool status in 50ms nodepool_nto_performanceprofile_test.go:255: Deleting configmap reference from nodepool ... nodepool_nto_performanceprofile_test.go:262: Successfully waited for performance profile ConfigMap to be deleted in 3.05s nodepool_nto_performanceprofile_test.go:281: Ending NTO PerformanceProfile test: OK nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-ntoperformanceprofile to have correct status in 50ms

nodepool_autorepair_test.go:43: test only supported on platform AWS

nodepool_day2_tags_test.go:44: test only supported on platform AWS

nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade in 12m48.05s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade to have correct status in 50ms nodepool_upgrade_test.go:160: Validating all Nodes have the synced labels and taints nodepool_upgrade_test.go:163: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade to have version 4.21.0-0.ci-2025-11-10-035626 in 50ms nodepool_upgrade_test.go:180: Updating NodePool image. Image: registry.build01.ci.openshift.org/ci-op-tjjzqxdw/release@sha256:a6ad9f64729aae6bf95775829ffb3225efc658c7c49411bb3ae4f0ac13547be4 nodepool_upgrade_test.go:187: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade to start the upgrade in 3.05s nodepool_upgrade_test.go:200: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade to have version 4.21.0-0.ci-2025-11-10-183549-test-ci-op-tjjzqxdw-latest in 6m57.05s util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade in 9.075s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-inplaceupgrade to have correct status in 50ms

nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-5xxnt in 9m42.075s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-5xxnt to have correct status in 3.05s nodepool_prev_release_test.go:55: NodePoolPrevReleaseCreateTest tests the creation of a NodePool with previous OCP release. nodepool_prev_release_test.go:57: Validating all Nodes have the synced labels and taints nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-5xxnt to have correct status in 50ms

nodepool_prev_release_test.go:31: Starting NodePoolPrevReleaseCreateTest. util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-fs6nf in 15m12.05s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-fs6nf to have correct status in 50ms nodepool_prev_release_test.go:55: NodePoolPrevReleaseCreateTest tests the creation of a NodePool with previous OCP release. nodepool_prev_release_test.go:57: Validating all Nodes have the synced labels and taints nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-fs6nf to have correct status in 50ms

nodepool_upgrade_test.go:100: starting test NodePoolUpgradeTest util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-replaceupgrade in 7m45.025s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-replaceupgrade to have correct status in 50ms nodepool_upgrade_test.go:160: Validating all Nodes have the synced labels and taints nodepool_upgrade_test.go:163: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-replaceupgrade to have version 4.21.0-0.ci-2025-11-10-035626 in 50ms nodepool_upgrade_test.go:180: Updating NodePool image. Image: registry.build01.ci.openshift.org/ci-op-tjjzqxdw/release@sha256:a6ad9f64729aae6bf95775829ffb3225efc658c7c49411bb3ae4f0ac13547be4 nodepool_upgrade_test.go:187: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-replaceupgrade to start the upgrade in 3.05s

nodepool_machineconfig_test.go:55: Starting test NodePoolMachineconfigRolloutTest util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-machineconfig in 12m36.1s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-machineconfig to have correct status in 50ms util.go:456: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-machineconfig to start config update in 50ms

util.go:542: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-rolling-upgrade in 19m27.05s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-rolling-upgrade to have correct status in 3.05s nodepool_rolling_upgrade_test.go:89: Successfully waited for NodePool e2e-clusters-cl6qt/node-pool-bqz57-test-rolling-upgrade to start the rolling upgrade in 3.05s

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cl6qt/node-pool-bqz57 in 2m57.05s util.go:298: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-bqz57.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:360: Successfully waited for a successful connection to the guest API server in 17.25s util.go:542: Successfully waited for 0 nodes to become ready in 75ms util.go:2836: Successfully waited for HostedCluster e2e-clusters-cl6qt/node-pool-bqz57 to have valid conditions in 8m12.05s

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cl6qt/node-pool-bqz57 in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms

util.go:542: Successfully waited for 0 nodes to become ready for NodePool e2e-clusters-cl6qt/node-pool-bqz57 in 125ms

util.go:3971: Successfully validated configuration authentication status consistency across HCP, HC, and guest cluster

nodepool_test.go:143: tests only supported on platform KubeVirt

hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-qxmzd/node-pool-wjpzh in 2m23s

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qxmzd/node-pool-wjpzh in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 25ms

nodepool_additionalTrustBundlePropagation_test.go:39: Starting AdditionalTrustBundlePropagationTest. util.go:542: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-qxmzd/node-pool-wjpzh-test-additional-trust-bundle-propagation in 5m39.05s nodepool_test.go:358: Successfully waited for NodePool e2e-clusters-qxmzd/node-pool-wjpzh-test-additional-trust-bundle-propagation to have correct status in 50ms

nodepool_additionalTrustBundlePropagation_test.go:73: Updating hosted cluster with additional trust bundle. Bundle: additional-trust-bundle nodepool_additionalTrustBundlePropagation_test.go:81: Successfully waited for Waiting for NodePool e2e-clusters-qxmzd/node-pool-wjpzh-test-additional-trust-bundle-propagation to begin updating in 10.05s nodepool_additionalTrustBundlePropagation_test.go:95: Successfully waited for Waiting for NodePool e2e-clusters-qxmzd/node-pool-wjpzh-test-additional-trust-bundle-propagation to stop updating in 11m20.05s nodepool_additionalTrustBundlePropagation_test.go:113: Updating hosted cluster by removing additional trust bundle. nodepool_additionalTrustBundlePropagation_test.go:127: Successfully waited for Waiting for control plane operator deployment to be updated in 75ms nodepool_additionalTrustBundlePropagation_test.go:148: Successfully waited for Waiting for NodePool e2e-clusters-qxmzd/node-pool-wjpzh-test-additional-trust-bundle-propagation to begin updating in 10.05s

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qxmzd/node-pool-wjpzh in 2m57.075s util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 8.375s util.go:542: Successfully waited for 0 nodes to become ready in 75ms util.go:2836: Successfully waited for HostedCluster e2e-clusters-qxmzd/node-pool-wjpzh to have valid conditions in 8m21.075s

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qxmzd/node-pool-wjpzh in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms

util.go:542: Successfully waited for 0 nodes to become ready for NodePool e2e-clusters-qxmzd/node-pool-wjpzh in 125ms

util.go:3971: Successfully validated configuration authentication status consistency across HCP, HC, and guest cluster

control_plane_upgrade_test.go:26: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-tjjzqxdw/release@sha256:4a697fd6926bf0bdea865156c99839b116f3329961d2aa036bb5546675685b38, toImage: registry.build01.ci.openshift.org/ci-op-tjjzqxdw/release@sha256:a6ad9f64729aae6bf95775829ffb3225efc658c7c49411bb3ae4f0ac13547be4 hypershift_framework.go:423: Successfully created hostedcluster e2e-clusters-5skst/control-plane-upgrade-bffb7 in 2m15s util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 in 3m51.05s util.go:298: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-control-plane-upgrade-bffb7.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF util.go:360: Successfully waited for a successful connection to the guest API server in 34.2s util.go:542: Successfully waited for 2 nodes to become ready in 9m18.075s util.go:575: Successfully waited for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 to rollout in 5m3.075s util.go:2836: Successfully waited for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 to have valid conditions in 50ms util.go:542: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-5skst/control-plane-upgrade-bffb7 in 200ms util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 in 75ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:3971: Successfully validated configuration authentication status consistency across HCP, HC, and guest cluster util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 25ms control_plane_upgrade_test.go:48: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-tjjzqxdw/release@sha256:a6ad9f64729aae6bf95775829ffb3225efc658c7c49411bb3ae4f0ac13547be4

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms util.go:360: Successfully waited for a successful connection to the guest API server in 25ms control_plane_upgrade_test.go:48: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-tjjzqxdw/release@sha256:a6ad9f64729aae6bf95775829ffb3225efc658c7c49411bb3ae4f0ac13547be4

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 in 3m51.05s util.go:298: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-control-plane-upgrade-bffb7.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF util.go:360: Successfully waited for a successful connection to the guest API server in 34.2s util.go:542: Successfully waited for 2 nodes to become ready in 9m18.075s util.go:575: Successfully waited for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 to rollout in 5m3.075s util.go:2836: Successfully waited for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 to have valid conditions in 50ms

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 in 50ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms

util.go:281: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5skst/control-plane-upgrade-bffb7 in 75ms util.go:298: Successfully waited for kubeconfig secret to have data in 50ms

util.go:542: Successfully waited for 2 nodes to become ready for NodePool e2e-clusters-5skst/control-plane-upgrade-bffb7 in 200ms

util.go:3971: Successfully validated configuration authentication status consistency across HCP, HC, and guest cluster