Description of problem:

In https://issues.redhat.com/browse/RHODS-6513 we documented that it's "not recommended". 

Sadly, customers will press buttons randomly, often, before reading the documentation. 

mflinn@redhat.com  and I just confirmed that after you install Managed RHODS in ROSA, if you go to Operator Hub, you see RHODS, and it looks like it's not installed. An average OpenShift admin might think "hum, that did not work, let me try to install from here!". 

If they do that, they will have effectively installed Managed RHODS first, and then Self-managed, in the same cluster. 

Since this is not supported/tested/desired, we should make it so that once you have installed one flavor of RHODS in your cluster, it should be impossible to install the other, unless you first fully uninstall the older one. 

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

Steps to Reproduce

1. <steps>

Actual results:

Expected results:

Reproducibility (Always/Intermittent/Only Once):

Build Details:

Workaround:

Additional info: