Bug 2262376

Summary: OCS Client operator is not listed in the UI due to the non-standalone annotation, making upgrade through UI impossible
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Neha Berry <nberry>
Component: ocs-client-operatorAssignee: Madhu Rajanna <mrajanna>
Status: CLOSED ERRATA QA Contact: Jilju Joy <jijoy>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.15CC: mrajanna, muagarwa, odf-bz-bot, omitrani
Target Milestone: ---Keywords: AutomationTriaged
Target Release: ODF 4.15.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: isf-provider
Fixed In Version: 4.15.0-147 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2268386 (view as bug list) Environment:
Last Closed: 2024-03-19 15:32:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2268386    

Description Neha Berry 2024-02-02 09:42:08 UTC 
Created attachment 2014545 [details]
Screenshot from UI

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
Comment 12 errata-xmlrpc 2024-03-19 15:32:31 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