Bug 1686036

Summary:	Bad navigation in installed operator information page on Web console
Product:	OpenShift Container Platform	Reporter:	Mike Fiedler <mifiedle>
Component:	Management Console	Assignee:	Jeff Phillips <jephilli>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.1.0	CC:	aos-bugs, jiazha, jokerman, mmccomas, rmeggins, spadgett, yapei
Target Milestone:	---
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The navigation path for the operator was using the name of the operator which is not the same as the name of the CSV in all cases. Consequence: When navigating from the detail view of the operator to the installed CSV, the filter would not include the CSV and no CSV was shown. Fix: Update the navigation to use the name of the installed CSV Result: The CSV view is now filtered correctly and the desired CSV is now shown.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-11 16:31:25 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:

Description Mike Fiedler 2019-03-06 15:15:06 UTC

Description of problem:

The console guys thinks this should go to Logging since the navigation comes from operator metadata, but please reroute as needed

From OperatorHub, click Cluster Logging operator.   In the "Installed Operator" highlight box there is this line:

This Operator has been installed on the cluster. View it here.

"View it here" is a link to https://<console URL>/k8s/ns/default/clusterserviceversions?rowFilter-clusterserviceversion-status=Copied%2CInstallSucceeded&name=cluster-logging

which links to a "No Cluster Service Versions Found"  message on the Installed Operator page

"name=cluster-logging" should be name=clusterlogging which works


Version-Release number of selected component (if applicable): 4.0.0-0.nightly-2019-03-06-074438 


How reproducible: Always


Steps to Reproduce:
1. In the console, install Cluster Logging Operator from OperatorHub
2. Refresh to see the Installed decoration on the operator
3. Click the operator in Operator Hub and click "View it here"

Actual results:

No cluster logging resources found


Expected results:

Display installed operator

Additional info:

Comment 1 Jeff Cantrill 2019-03-06 15:54:53 UTC

Moving to OLM as Logging doesn't control any UI components from OperatorHub unless there is some CSV change required.

Comment 2 Jian Zhang 2019-03-07 05:25:45 UTC

Mike,

Thanks for your report! Other operators have the same issue. I think this is a UI issue. Moving to "Management Console".
Reproduce steps:
1) Catalog ->Operator Hub-> Couchbase Operator(or any other operators) -> Install
2) Catalog -> Operator Hub-> Coucabase Operator(or your installed Operators) -> We can see the notes: "This Operator has been installed on the cluster. View it here." -> Click the `View it here` link. Actually, no installed Operator display.

Comment 3 Jian Zhang 2019-03-07 07:09:34 UTC

>  Other operators have the same issue.

Sorry, my mistake, etcd-operator doesn't have this issue, but the Couchbase does have. Many operators have this issue, but not all.
The root cause is the filter strings in the search bar. For example, the strings are `cluster-logging` after clicking the `View it here` link.
But, the csv name of the Cluster Logging is `clusterlogging.v0.0.1`, so we got nothing.
So we should change the searching strings.

Comment 4 Samuel Padgett 2019-03-08 20:08:12 UTC

Jeff, can you investigate?

Comment 5 Samuel Padgett 2019-03-08 22:18:03 UTC

https://github.com/openshift/console/pull/1274

Comment 6 Yadan Pei 2019-03-11 06:36:36 UTC

This is fixed on 

$ oc image info registry.svc.ci.openshift.org/ocp/4.0-2019-03-10-103624@sha256:34de36b056aa48451c74d8812543e81c081d688cdc1feee38f68b84de2385559 | grep commit
             io.openshift.build.commit.id=e9e6e216b078e86604ae41fdd37d3da2a0c59d8b



1. Install Cluster Logging, Couchbase Operator via Catalog -> Operator Hub
2. Catalog -> Operator Hub -> Installed, click one operator, it shows "This Operator has been installed on the cluster. View it here." 
3. click on the link 'View it here', it redirects user to https://<console_url>/k8s/ns/yapei/clusterserviceversions?rowFilter-clusterserviceversion-status=Copied%2CInstallSucceeded&name=clusterlogging.v0.0.1
https://<console_url>/k8s/ns/yapei/clusterserviceversions?rowFilter-clusterserviceversion-status=Copied%2CInstallSucceeded&name=couchbase-operator.v1.1.0

Correct filter name is used.