Bug 1659921 - OperatorGroup should have a link on ClusterServiceVersion Overview
Summary: OperatorGroup should have a link on ClusterServiceVersion Overview
Keywords:
Status: VERIFIED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Alec Merdler
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-17 08:22 UTC by XiaochuanWang
Modified: 2019-08-23 05:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description XiaochuanWang 2018-12-17 08:22:03 UTC 
Description of problem:
Make sure there is an OperatorGroup under a project such as openshift-operator-lifecycle-manager. Go to the project and check CSV overview page for Operator Group, this does not have a link.

Version-Release number of selected component (if applicable):
https://github.com/openshift/console with source commit 92dea42f78c93e1a4cd9995b037245f242d57269
Image Id: 071aa364c87d

How reproducible:
Always

Steps to Reproduce:
1. Make sure there is an OperatorGroup under a project such as openshift-operator-lifecycle-manager. Could check CRD page: k8s/all-namespaces/operators.coreos.com~v1alpha2~OperatorGroup

2. Follow the link to the project openshift-operator-lifecycle-manager
3. Create a subscription and make sure it's InstallSucceeded such as "Package Server". Check the CSV overview page.

Actual results:
3. The OperatorGroup does not have a link, it only displays "olm-operators"

Expected results:
3. The OperatorGroup "olm-operators" should have a link such as k8s/ns/openshift-operator-lifecycle-manager/operators.coreos.com~v1alpha2~OperatorGroup/olm-operators.

Additional info:
Comment 1 Alec Merdler 2018-12-17 20:21:30 UTC 
This is intended behavior until we have UI design for interacting with the `OperatorGroup` resource.
Note You need to log in before you can comment on or make changes to this bug.