Bug 2268393 - [Backport to 4.14.z] ODF client operator has nondescript information on the operator hub
Summary: [Backport to 4.14.z] ODF client operator has nondescript information on the o...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ocs-client-operator
Version: 4.14
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Madhu Rajanna
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On: 2278843 2267712
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-07 09:02 UTC by Neha Berry
Modified: 2024-05-07 06:34 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2267712
Environment:
Last Closed: 2024-05-07 06:31:04 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage ocs-client-operator pull 99 0 None Merged Bug 2267712: [release-4.15] add description to client operator csv 2024-03-07 12:04:37 UTC

Description Neha Berry 2024-03-07 09:02:11 UTC
+++ This bug was initially created as a clone of Bug #2267712 +++

Cloning for tracking backport to 4.14.z 

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

Comment 3 krishnaram Karthick 2024-04-15 07:04:57 UTC
Moving the bug to 4.14.8 as we had had exceeded the fixes to be taken in 4.14.7.


Note You need to log in before you can comment on or make changes to this bug.