Impossible to install 2 awx on the same cluster in 2 different namespace with HELM

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that the AWX Operator is open source software provided for free and that I might not receive a timely response.

Bug Summary

I have 2 namespace : infra-int and infra-dev. AWX run in infra-dev.

When I try to install with helm the second AWX in infra-int I get the following message :

Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "awx-operator-metrics-reader" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "infra-int": current value is "infra-dev"

AWX Operator version

1.1.1

AWX version

21.10

Kubernetes platform

kubernetes

Kubernetes/Platform version

1.24.9

Modifications

no

Steps to reproduce

Install AWX in the first namespace (example: infra-dev). Then install the second AWX in another namespace (e.g. infra-int). The message in the bug summary appears. I asked about this on the forum and it seems that this type of installation is not a problem using make deploy or the Kustomization approach So it seems to be related to Helm only (I don't have enough expertise to say more, sorry)

Expected results

Have one awx under infra-int and another under infra-dev

Actual results

I have the message :

Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "awx-operator-metrics-reader" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "infra-int": current value is "infra-dev"

Additional information

No response

Operator Logs

No response