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.
https://github.com/red-hat-storage/ocs-client-operator/pull/28 posted the PR
Madhu, does it require a backport to 4.13 branch?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenShift Data Foundation 4.13.0 enhancement and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:3742