+++ This bug was initially created as a clone of Bug #2184605 +++ Description of problem (please be detailed as possible and provide log snippests): OpenShift Data Foundation Client operator is listed in OperatorHub and installable from UI. This need not be enabled in UI. Version of all relevant components (if applicable): OCP 4.12.9 $ oc get csv NAME DISPLAY VERSION REPLACES PHASE configure-alertmanager-operator.v0.1.518-ec4c3cd configure-alertmanager-operator 0.1.518-ec4c3cd configure-alertmanager-operator.v0.1.516-bdea4ea Succeeded observability-operator.v0.0.20 Observability Operator 0.0.20 observability-operator.v0.0.19 Succeeded ocs-client-operator.v4.13.0-124.stable OpenShift Data Foundation Client 4.13.0-124.stable Succeeded odf-csi-addons-operator.v4.13.0-124.stable CSI Addons 4.13.0-124.stable Succeeded route-monitor-operator.v0.1.493-a866e7c Route Monitor Operator 0.1.493-a866e7c route-monitor-operator.v0.1.489-7d9fe90 Succeeded ========================================================================== Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? User might choose to install the operator which is not recommented. The installation should not be enabled from UI. Is there any workaround available to the best of your knowledge? No Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes, always Can this issue reproduce from the UI? UI issue. If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Create Catalogsource for ODF 4.13.0 2. Try to install OpenShift Data Foundation Client operator from OperatorHub in UI Actual results: Installation of OpenShift Data Foundation Client operator is possible from UI Expected results: OpenShift Data Foundation Client operator should not be installable from UI Additional info: Didn't select component because a bug component for ocs-client-operator is not present. --- Additional comment from RHEL Program Management on 2023-04-05 07:41:42 UTC --- This bug having no release flag set previously, is now set with release flag 'odf‑4.13.0' to '?', and so is being proposed to be fixed at the ODF 4.13.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag. --- Additional comment from Jilju Joy on 2023-04-05 07:46:51 UTC --- --- Additional comment from Jilju Joy on 2023-04-05 07:47:22 UTC --- --- Additional comment from Madhu Rajanna on 2023-04-05 08:34:10 UTC --- https://github.com/red-hat-storage/ocs-client-operator/pull/28 posted the PR