Description of the Problem
In multiregion enabled env, User has tried to edit existing LDAP definition(Note: LDAP definition has added from non-mutiregion env due to existing bug OCMUI-2732 ) for a cluster from "Access control" tab > Identity providers section. This action reports type error as below.

console.js:36 TypeError: y.some is not a function
    at render (FormikFieldArray.tsx:62:40)
    at Oc (chrome-root.d6ec82adcca2f232.js:2:214535)
    at Pc (chrome-root.d6ec82adcca2f232.js:2:214333)
    at Sl (chrome-root.d6ec82adcca2f232.js:2:257677)
    at vs (chrome-root.d6ec82adcca2f232.js:2:245880)
    at ys (chrome-root.d6ec82adcca2f232.js:2:245808)
    at bs (chrome-root.d6ec82adcca2f232.js:2:245671)
    at os (chrome-root.d6ec82adcca2f232.js:2:242478)
    at ls (chrome-root.d6ec82adcca2f232.js:2:242867)
    at za (chrome-root.d6ec82adcca2f232.js:2:183766)
    at chrome-root.d6ec82adcca2f232.js:2:240415 

See the recording Screen Recording 2024-11-26 at 4.26.09 PM.movattached.

How reproducible:

Always

Steps to Reproduce:

1. Open OCM UI staging
2. Open a ready cluster.
3. Click "Access control" tab > Click "Identity providers".
4. Click "Add identity providers" > LDAP.
5. Fill the mandatory fields and click "Add".
6. Open OCM UI staging using https://console.dev.redhat.com/openshift/?multiregion=true 
7. Open the same cluster.
8. Go to "Access control" tab > Click "Identity providers".
9. Click kebab icon associated to the "LDAP" IDP (added in step 5).
10. Click "Edit" option and see the behavior.

Actual results:

At step 10 , Type error reported in the page as mentioned above.{}

Expected results:

At step 10 , LDAP form  should be successfully  loaded with existing definition for the update.