To Reproduce Steps to reproduce the behavior:

1. Go to any crc job in upstream and notice that the test-operator is installed both in openstack-operator namespace and openstack namespace.

Expected behavior

• The test-operator is present only in one namespace - openstack. Ci-framework test-operator role installs the test-operator there.

Bug impact

• This might lead to a situation when the two controllers are fighting over the creation of the pods. For example in this job build one can see that there are both pods created by the operator installed in the openstack namespace and the one installed in the openstack-operators namespace.
• I'm not sure what is the impact on the other jobs.

Additional context

• I've quickly skimmed through the latest job builds and it seems that the test-operator started to appear in the openstack-operators namespace around January 15th.
• I assume something must have changed around that time maybe in openstack-operator.

Reviews:

• https://github.com/openstack-k8s-operators/ci-framework/pull/2727
• https://github.com/openstack-k8s-operators/test-operator/pull/282