This bug is cloned in documentation for coming up with the content for the UI page We can use this doc to work on the content together and once it is finalized, we can ask to proceed with making those changes in the UI Operator description page https://docs.google.com/document/d/1lXPJE2Cr48AtW0x5SlzbrNOexRvoWSV1iF8-StFpckQ/edit#heading=h.pzkfd5kiolke +++ This bug was initially created as a clone of Bug #2276028 +++ +++ This bug was initially created as a clone of Bug #2267712 +++ Description of problem: With OCP 4.15 GA, the Operator Hub lists the 'OpenShift Data Foundation Client' operator as requested in bug 2262376, but the information for the operator is nondescript - 'foo'. See attached screenshot It should be replaced with something like: "This operator is not intended to be directly installed" Version-Release number of selected component (if applicable): OCP 4.15 GA --- Additional comment from RHEL Program Management on 2024-03-04 15:50:37 UTC --- This bug having no release flag set previously, is now set with release flag 'odf‑4.15.0' to '?', and so is being proposed to be fixed at the ODF 4.15.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 Madhu Rajanna on 2024-03-04 15:57:34 UTC --- Need change at https://github.com/red-hat-storage/ocs-client-operator/blob/09ed5addd2f789ea17ddb0[…]/manifests/bases/ocs-client-operator.clusterserviceversion.yaml, This is present from Day 1 nothing changed recently --- Additional comment from Mudit Agarwal on 2024-03-05 08:03:56 UTC --- Not a 4.15 release blocker --- Additional comment from RHEL Program Management on 2024-03-05 09:00:41 UTC --- This BZ is being approved for ODF 4.15.0 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'odf‑4.15.0 --- Additional comment from RHEL Program Management on 2024-03-05 09:00:41 UTC --- Since this bug has been approved for ODF 4.15.0 release, through release flag 'odf-4.15.0+', the Target Release is being set to 'ODF 4.15.0 --- Additional comment from Jilju Joy on 2024-03-05 10:44:06 UTC --- Do we need a different description for the operator other than the one suggested in comment #0 ? Asking because the client cluster in provider-client configuration can make use of UI to install the operator. --- Additional comment from Jilju Joy on 2024-03-05 11:24:31 UTC --- (In reply to Jilju Joy from comment #6) > Do we need a different description for the operator other than the one > suggested in comment #0 ? Asking because the client cluster in > provider-client configuration can make use of UI to install the operator. Removing needinfo as this got clarified. --- Additional comment from errata-xmlrpc on 2024-03-06 05:10:06 UTC --- This bug has been added to advisory RHSA-2023:118688 by Deepshikha Khandelwal (dkhandel) --- Additional comment from errata-xmlrpc on 2024-03-06 05:10:22 UTC --- Bug report changed to ON_QA status by Errata System. A QE request has been submitted for advisory RHSA-2023:118688-01 https://errata.engineering.redhat.com/advisory/118688 --- Additional comment from Jilju Joy on 2024-03-07 09:11:34 UTC --- Verified in 4.15.0-157. OpenShift Data Foundation Client in OperatorHub page is showing correct description. Screenshot attached. --- Additional comment from errata-xmlrpc on 2024-03-19 15:33:18 UTC --- 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 (Important: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & 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/RHSA-2024:1383 --- Additional comment from RHEL Program Management on 2024-04-19 05:25:09 UTC --- This bug having no release flag set previously, is now set with release flag 'odf‑4.16.0' to '?', and so is being proposed to be fixed at the ODF 4.16.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 RHEL Program Management on 2024-04-19 05:25:09 UTC --- The 'Target Release' is not to be set manually at the Red Hat OpenShift Data Foundation product. The 'Target Release' will be auto set appropriately, after the 3 Acks (pm,devel,qa) are set to "+" for a specific release flag and that release flag gets auto set to "+". --- Additional comment from Jilju Joy on 2024-04-19 05:31:45 UTC --- The information can be more detailed like OCS and ODF operator. Currently it is a single statement in 4.15. --- Additional comment from RHEL Program Management on 2024-04-22 10:45:46 UTC --- This BZ is being approved for ODF 4.16.0 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'odf‑4.16.0 --- Additional comment from RHEL Program Management on 2024-04-22 10:45:46 UTC --- Since this bug has been approved for ODF 4.16.0 release, through release flag 'odf-4.16.0+', the Target Release is being set to 'ODF 4.16.0