Description of problem (please be detailed as possible and provide log snippests): odf-console is not enabled in the cluster, unless the MCO operator plugin is disabled, when MCO is deployed prior to ODF operator Version of all relevant components (if applicable): OCP: 4.13.0 odf-multicluster-orchestrator: v4.13.0-203.stable odf-operator :v4.13.0-203.stable odr-hub-operator: v4.13.0-203.stable ACM: 2.7.3 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Yes Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Deploy OCP,ACM, MCO and then install ODF operator 2. 3. Actual results: odf-console is not enabled in the cluster Expected results: odf-console should be enabled in the cluster Additional info:
Is this a bug or expected behavior?
I believe plugins weren't designed to be deployed on the same cluster as ODF. Since our assumption was that hub cluster will not have ODF on it. So it is an expected behavior. If our support statement has changed and we now support such deployments, this is an enhancement request. @gshanmug What do you think? We might need to push it out all the way to 4.15.
If you have installed ODF from OperatorHub UI, make sure that the "Enable" option is selected for the "Console plugin". If CatalogSource of the operator is "redhat-operators" then this option will be auto-selected for you, else it will be disabled by default and you need to enable it. If u have installed ODF via CLI, then you need to EITHER: Go to "Installed Operators > Operator details" page. And enable Console plugin (option should be there on right hand section of the screen). Wait for pop-up as stated above and refresh via it. OR: Run "oc patch consoles.operator.openshift.io cluster --patch '{ "spec": { "plugins": ["odf-console"] } }' --type=merge" Wait for pop-up as stated above and refresh via it. If in your cluster, you installed ODF from "redhat-operators" CatalogSource using the OperatorHub UI (and "Console plugin" option was enabled while instillation) then this is something we need to investigate further and fix it if needed.
moving to 4.14 as not a blocker...