Bug 1990282

Summary: 'Install' button enables to proceed with installation of multiple ocs-opertor under different namespace in a cluster
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Aman Agrawal <amagrawa>
Component: ocs-operatorAssignee: Jose A. Rivera <jrivera>
Status: CLOSED NOTABUG QA Contact: Raz Tamir <ratamir>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.8CC: madam, ocs-bugs, odf-bz-bot, sostapov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-15 15:01:45 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
ocs-operator via UI none

Description Aman Agrawal 2021-08-05 07:41:20 UTC 
Created attachment 1811133 [details]
ocs-operator via UI

Description of problem (please be detailed as possible and provide log
snippests):


Version of all relevant components (if applicable):


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


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


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


Steps to Reproduce:
1. Deploy a 4.8 OCS cluster via Jenkins.
2. Login to UI console and go to Operators -> OperatorsHub.
3. Search with OCS, make sure you have 2 instances of ocs-operator, in my case I could see 2 instances of ocs-operator without pushing another image of it by editing catalogsource.
4. Both the ocs-operator show 'Install' button on them whereas the cluster already had a ocs-operator installed when OCS was deployed via Jenkins.
5. Click on Install, select a different namespace and proceed with installation.
6. The installation will fail at the end.

7. Also found this issue on another cluster where only one instance of ocs-operator was available and I pushed another image of it by editing the catalogsource.
8. Went back to UI, under Operators -> OperatorsHub and search with OCS. Both the ocs-operator will now show 'Install' button on them whereas the cluster already has a ocs-operator installed when OCS was deployed via Jenkins.
9. Click on Install, select a different namespace and proceed with installation.
10. The installation will fail at the end.


Actual results: ocs-operator on UI has 'Install' button when we have multiple instances of it and one instance is already installed


Expected results: No matter the number of instances of ocs-operator available on UI even if new ocs-operator image is pushed later on by editing the catalogsource, they should always show 'Uninstall' button when one instance of ocs-operator is already installed on the cluster


Additional info:

Found the issue on these 2 clusters-
https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster/4970/

https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster/4324/
Comment 3 Jose A. Rivera 2021-10-15 15:01:45 UTC 
This is a "feature" of the OLM, and thus working as intended. Most of this is an artifact of the fact that we're doing non-GA stuff under the hood for our testing. There's not much we can (or should!) do about it. Closing as NOTABUG.