To Reproduce Steps to reproduce the behavior:

1. Mistakenly install a service operator (such as RHOSO Test operator) in the openstack namespace instead of openstack-operators namespace
2. Create and apply an "OpenStack" resource
3. Notice via "oc get pods n openstack{}operators" that the OpenStack operator pod is crash looping, and that the service operators are never deployed

Expected behavior

• When the "OpenStack" resource is created, the OpenStack service operators should be deployed

Bug impact

• This can prevent users from finishing OpenStack operator installation

Known workaround

• Delete bad operators found in "oc get operators -o yaml".  These are "bad" only in respect to what our code is expecting, but it is actually our code that needs to be fixed.