When an OpenStackBaremetalSet is created in a target namespace, any generated cloud-init Secrets for selected Metal3 BaremetalHosts will be also be created in the same namespace as the OpenStackBaremetalSet.  This creates a problem for the Metal3 operator if its associated Provisioning resource does not have "watchAllNamespaces: true", because the RHOSO-generated cloud-init Secrets will most likely belong to some other namespace than "openshift-machine-api" (which is the only namespace Metal3 operator watches and for which it has cached resources).

We should either document that the Metal3 Provisioning resource needs to be updated to have "watchAllNamespaces: true" or we should refactor the OpenStack Baremetal operator so that it always generates the Secrets in the Metal3 operator's namespace.