Description of problem:

If I install self-managed RHODS in my OSD/ROSA cluster, OCM still allows me to trigger Addon installation.

After seeing the Addon failed status, I can check the cluster and notice the existent SM installation. At the point, if I uninstall Addon from OCM, I would end up removing SM installation too.

Can the addon be improved to capture any existing installation of RHODS that was done outside OCM?

Prerequisites (if any, like setup, operators/versions):

Create a OSD

Steps to Reproduce

1. install RHODS Self-managed
2. trigger Addon installation from OCM
3. check the status of addon installation
4. trigger uninstall from OCM
5. check the status of Self-managed installation in the cluster

Actual results:

• Addon installation can be triggered even if the cluster has self-managed RHODS installed
• Uninstalling the (failed) addon would unistall Self-managed too

Expected results:

Addon installation is blocked if self-managed is alredy installed

Reproducibility (Always/Intermittent/Only Once):

Always: tried in a OSD cluster, but it should be likely valid for ROSA too because the addons are installed in the same way (we'll check that anyway)

Build Details:

RHODS 1.20 and 1.21

Workaround:

N/A

Additional info:

• after addon installation is triggered, the cluster have 2 CSV for RHODS. The one for SM gets the Failed status with this reasons: "csv created in namespace with multiple operatorgroups, can't pick one automatically". The one for CloudService remains in "unknown" status
• see the attached logs extracted from rhods-operator and addon-managed-odh-catalog pods