When the machines try to get the resourcePoolPath, it finds multiple resource pools and is unable to resolve the right one. Adding a property in the machine sets with the resourcePoolPath information so the right one is picked.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.5.6 bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:3330
Verified on nightly build 4.5.0-0.nightly-2020-08-07-024812 and passed. # oc get machinesets.machine.openshift.io jima45ipi0808-hdhxz-worker -n openshift-machine-api --template '{{.spec.template.spec.providerSpec.value.workspace.resourcePool}}' /dc1/host/devel/Resources