Bug 2042140

Summary: OCS/ODF operator missing from UI
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: swilson
Component: odf-operatorAssignee: Nitin Goyal <nigoyal>
Status: CLOSED NOTABUG QA Contact: Elad <ebenahar>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.9CC: jrivera, muagarwa, ocs-bugs, odf-bz-bot
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-19 05:21:29 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:
Attachments:
Description Flags
oc get csv -n openshift-storage
none
'oc get csv -n openshift-storage' none

Description swilson 2022-01-18 20:37:35 UTC 
Description of problem (please be detailed as possible and provide log
snippests):
OCS/ODF operator missing from UI

Version of all relevant components (if applicable):
OCP4.8, OCP4.9, OCS4.8, OCS4.9

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
May impact GitOps workflow.

Is there any workaround available to the best of your knowledge?
Delete one of the CSV subscriptions. StorageCluster seems unaffected.

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

Can this issue reproduce from the UI?
Yes

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Deploy OCP4.8.
2. Install OCS4.8 operator with channel: Stable-4.8.
3. Upgrade OCP4.8 to OCP4.9.
4. Change OCS operator from Stable-4.8 channel to Stable-4.9 channel.
5. openshift-storage pods are restarted(upgraded).
6. OCS operator disappears from UI. OCS operator still visible on CLI
7. Install ODF4.9 operator with Stable-4.9 channel.
8. ODF4.9 operator is shown in UI. Both OCS4.9 and ODF4.9 CSVs are shown on CLI


Actual results:
Both the OCS4.9 and ODF4.9 CSV show on CLI. ODF4.9 operator shows in UI.

Expected results:
Only ODF4.9 shown in UI and CLI


Additional info: 
Naming issue could have an impact on customer GitOps management of OCS/ODF operators.
Comment 2 swilson 2022-01-18 20:53:49 UTC 
Created attachment 1851695 [details]
oc get csv -n openshift-storage
Comment 3 swilson 2022-01-18 20:55:52 UTC 
Created attachment 1851708 [details]
'oc get csv -n openshift-storage'

'oc get csv -n openshift-storage'
Comment 4 Nitin Goyal 2022-01-19 05:21:29 UTC 
This is working as expected, we are hiding CSV's in the UI intentionally.
Comment 5 Jose A. Rivera 2022-01-19 15:12:30 UTC 
I'll also note that the procedure described is incorrect. The upgrade path from OCS 4.8 to ODF 4.9 (there's no such thing as OCS 4.9, from a customer perspective) is to install ODF from Operator Hub. The new odf-operator will take care of upgrading the ocs-operator CSV.
Comment 6 swilson 2022-01-19 15:45:48 UTC 
Please review the attached picture. If the customer runs `oc get csv -n openshift-storage`, they will see "ocs-operator.v4.9.1" and "odf-operator.v4.9.1". This can be confusing. Will customers need to adjust their Helm charts and YAML manifests within their GitOps workflow to account for the new name?