+++ This bug was initially created as a clone of Bug #2262376 +++

Cloning the bug for 4.14.z release

Description of problem:
========================

Tested on both ODF 4.15.0-126 build and ODF 4.14.5-2-fusion-hci build.

We have the ons-storage-client operator installed in the ocs-storage-client namespace but in UI we get No operator found

This inhibits us from performing standalone upgrade of the Operator from UI

More discussion between Stakeholders here - https://ibm-systems-storage.slack.com/archives/C05RJB6H0LQ/p1706776816320899 

Version-Release number of selected component (if applicable):
============================================================
ODF 4.15 and ODF 4.14.5-2 (fusion-hci build)

OCP 4.15.9

How reproducible:
=================
Always

Steps to Reproduce:
====================
1. Create a provider/client configuration following the docs [1] and [2]
2. Install the ocs-client-operator from the CLI [yaml at [3] as it is not listed under the Operator Hub 
3. Check for the operator listed in the client namespace we create or even under all-namespaces

[1] https://docs.google.com/document/d/1uVjzJQFv_t1Fymb-hgMhNd6pve8fkbrxp1TadU5wv9I/edit?pli=1

[2] https://docs.google.com/document/d/1RfDNQi4B3x4kv9PXx2lqGSD2V2UGideTCIXqLYJFg0Y/edit?pli=1#heading=h.bebinah79b8e


Actual results:
=================
The operator is not listed in the UI

Expected results:
=================
To be able to upgrade the Operator from UI, we will need the operator to be listed in the UI

Additional info:
==================
[3]


---
apiVersion: v1
kind: Namespace
metadata:
  name: openshift-storage-client
---
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: openshift-storage-client-operator-group
  namespace: openshift-storage-client
spec:
  targetNamespaces:
    - openshift-storage-client
---
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: ocs-client-operator
  namespace: openshift-storage-client
spec:
  channel: stable-4.15
  installPlanApproval: Automatic
  name: ocs-client-operator
  source: ocs-catalogsource
  sourceNamespace: openshift-marketplace
---
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ocs-catalogsource
  namespace: openshift-marketplace
  labels:
    ocs-operator-internal: "true"
spec:
  displayName: Openshift Container Storage
  image: quay.io/rhceph-dev/ocs-registry:4.15.0-126
  publisher: Red Hat
  sourceType: grpc
  priority: 100

--- Additional comment from RHEL Program Management on 2024-02-02 09:42:23 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 RHEL Program Management on 2024-02-05 04:59: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-02-05 04:59: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 Sunil Kumar Acharya on 2024-02-13 08:42:35 UTC ---

Please update the RDT flag/text appropriately.

--- Additional comment from Madhu Rajanna on 2024-02-13 11:54:02 UTC ---

No doc update as its was done on purpose and we are fixing this for ODF/HCI clusters

--- Additional comment from errata-xmlrpc on 2024-02-21 02:08:50 UTC ---

This bug has been added to advisory RHBA-2023:118688 by ceph-build service account (ceph-build.COM)

--- Additional comment from Jilju Joy on 2024-03-04 16:04:02 UTC ---

Tested in version 4.15.0-150. Operator "Openshift Data Foundation Operator Client" is visible in OperatorHub and Install option is enabled. The operator is listed in "Installed Operators" page as well.
Screenshots attached.

Tested in a client cluster on Provider-Client configuration.

Madhu,
The description of the operator is just "foo". Is this a problem. I see there is another bug https://bugzilla.redhat.com/show_bug.cgi?id=2267712 for this.

--- Additional comment from Jilju Joy on 2024-03-04 16:05:15 UTC ---

Screenshot showing OpenShift Data Foundation Client operator in OperatorHub page

--- Additional comment from Madhu Rajanna on 2024-03-04 16:06:35 UTC ---

@Jilju yes we have a different bug to fix the description

--- Additional comment from Jilju Joy on 2024-03-05 07:54:42 UTC ---

(In reply to Madhu Rajanna from comment #9)
> @Jilju yes we have a different bug to fix the description

Thanks. Moving this to verified state based on coment #7.

--- Additional comment from Jilju Joy on 2024-03-05 07:56:58 UTC ---

Adding automation TriagedKeyword because this will be covered in UI deployment and upgrade of client clusters in provider-client configuration. A seperate test case is not required.