Cluster Autoscaler Cannot Match openstack:///UUID ProviderID to OVH NodePool

[RMrenex]

Which component are you using?:
/area cluster-autoscaler

What version of the component are you using?:
Component version: v1.33.0

What k8s version are you using (kubectl version)?:
Client Version: v1.32.2
Kustomize Version: v5.5.0
Server Version: v1.32.2

What environment is this in?:
OVH Public Cloud (managed Kubernetes), using the OVHcloud external cloud‑provider for node autoscaling.

What did you expect to happen?:
The Cluster Autoscaler should discover the OVH NodePool (min 3 / max 6), match each Kubernetes Node (with providerID = openstack:///UUID) to that pool, and perform scale‑up or scale‑down as needed.

What happened instead?:
In the autoscaler logs we repeatedly see:

trying to find node group of node <node‑name> (provider ID openstack:///UUID) by listing all nodes under autoscaled node pools  
unable to find which node group the node <node‑name> belongs to

Despite having created a valid OVH API token (with GET/POST/PUT/DELETE on /cloud/project//kube//nodepool* and /…/nodepool/{id}/nodes), the autoscaler never associates any NodeGroup, so no scaling occurs.

How to reproduce it (as minimally and precisely as possible):

1. Create an OVH Token with rights:
   GET /cloud/project/*/kube/*/nodepool
   POST /cloud/project/*/kube/*/nodepool
   GET /cloud/project/*/kube/*/nodepool/{nodePoolId}
   PUT /cloud/project/*/kube/*/nodepool/{nodePoolId}
   DELETE /cloud/project/*/kube/*/nodepool/{nodePoolId}
   GET /cloud/project/*/kube/*/nodepool/{nodePoolId}/nodes
2. Deploy a Kubernetes cluster on OVH Public Cloud.
3. Label your NodePool with spec.id=<NODEPOOL_ID>, set spec.autoscale=true, minNodes=3, maxNodes=6.
4. Deploy cluster-autoscaler v1.33.0 with args:

          command:
            - ./cluster-autoscaler
            - --v=6
            - --cloud-provider=ovhcloud
            - --cloud-config=/etc/kubernetes/cloud-config.json
            - --skip-nodes-with-local-storage=false
            - --skip-nodes-with-system-pods=false
            - --balance-similar-node-groups=true
            - --nodes=3:6:<NODE_POOL_ID>

and /etc/kubernetes/cloud-config.json containing the correct project_id (32‑hex) and cluster_id (UUID).
5. Observe the logs of the cluster-autoscaler Pod: you will see the “unable to find which node group…” error for each node.

Anything else we need to know?:

The OVH token has been created and tested against the OVH API; listing node pools and nodes works outside of the autoscaler.