Upon the creation of two ProvisioningRequests, only one of the ProvisioningRequests gets fulfilled. The other one reports "Hardware provisioning is in progress" all the time, and it does not report a failure due to a timeout. 

-   digest: sha256:51844ef5a1038ceefeedad949223e2f032ae3b1dc3614eae1a6fbb0de77c8c2b
    name: o-cloud-manager
    ocp_version: '4.20'
    pull_spec: quay.io/redhat-user-workloads/telco-5g-tenant/o-cloud-manager-fbc-4-20:latest
    timestamp: '2025-08-18T13:50:50Z'
    version: '4.20'
    

100%    

Apply a YAML file with the definition of two ProvisioningRequests (attached sample file)   

Two PRs are created, only one progresses:

[kni@registry ~]$ oc get oranpr -A
NAME                                   DISPLAYNAME   AGE   PROVISIONPHASE   PROVISIONDETAILS
73eee8f4-9fe2-44fd-be05-495f8efa082f   sno02         79m   progressing      Hardware provisioning is in progress
ae8d4f1e-ddfc-4939-aea0-f0411cb68697   sno03         79m   fulfilled        Provisioning request has completed successfully

It creates three AllocatedNodes, instead of two:

[kni@registry ~]$ oc get allocatednode -A
NAMESPACE    NAME                                             PLUGIN            NODEALLOCATIONREQUEST         HWMGR NODE ID   AGE   STATE
oran-o2ims   metal3-hwplugin-sno02-xr8620t-pool-xr8620t-245   metal3-hwplugin   metal3-493f7c0cae314435967d   xr8620t-245     77m   Completed
oran-o2ims   metal3-hwplugin-sno03-xr8620t-pool-xr8620t-245   metal3-hwplugin   metal3-0ec32a14c3104fca9e6b   xr8620t-245     77m   Completed
oran-o2ims   metal3-hwplugin-sno03-xr8620t-pool-xr8620t-246   metal3-hwplugin   metal3-0ec32a14c3104fca9e6b   xr8620t-246     77m   Completed

The two PRs should succeed, and at least the failing one should report a failure after the timeout. I would expect as well to see only two Allocated nodes.

Logs and must-gather available at: https://drive.google.com/drive/folders/1Iv89RYZrMhiqxGuEgRTlzjLT7AXSr_rZ?usp=sharing