OVN-Kubernetes assigns duplicate node-subnet to the RHOCP nodes in case of clusterNetwork ranges run out

Issue

• Why is the RHOCP cluster facing timeout occurrences in the communication between pods and services?

• Why are the RHOCP nodes installed with duplicate assigned node-subnets?

  $ oc get nodes -oyaml | grep subnet | sort 
    k8s.ovn.org/node-subnets: '{"default":["10.xxx.0.0/22"]}'
    k8s.ovn.org/node-subnets: '{"default":["10.xxx.12.0/22"]}'
    k8s.ovn.org/node-subnets: '{"default":["10.xxx.16.0/22"]}' <---
    k8s.ovn.org/node-subnets: '{"default":["10.xxx.16.0/22"]}' <---
    k8s.ovn.org/node-subnets: '{"default":["10.xxx.16.0/22"]}' <---
    k8s.ovn.org/node-subnets: '{"default":["10.xxx.28.0/22"]}'
    k8s.ovn.org/node-subnets: '{"default":["10.xxx.32.0/22"]}'