Bug 1980182 - The installed operator UI is not working correctly when there are multiple versions defined in the operator's CRD
Summary: The installed operator UI is not working correctly when there are multiple ve...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.6
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
: 4.6.z
Assignee: Bryan Florkiewicz
QA Contact: Yanping Zhang
URL:
Whiteboard:
Depends On: 1888036
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-08 03:33 UTC by Longlong Cao
Modified: 2021-08-04 19:59 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
OCP4.6.26 on AWS
Last Closed: 2021-08-04 19:59:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
multiple versions CRD in the installed operator can not be shown correctly in the installed operator details page. (107.22 KB, image/png)
2021-07-08 03:33 UTC, Longlong Cao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 9549 0 None open Bug 1980182: operator UI not working with multiple version CRD in 4.6 2021-07-20 13:44:41 UTC
Red Hat Product Errata RHBA-2021:2886 0 None None None 2021-08-04 19:59:37 UTC

Description Longlong Cao 2021-07-08 03:33:43 UTC
Created attachment 1799521 [details]
multiple versions CRD in the installed operator can not be shown correctly in the installed operator details page.

Description of problem:

After install operator with multiple version in its CRD from operator hub on OCP 4.6, then switch to the installed operator details page, we found that the UI will show multiple tab for the corresponding CR.
If we click one of the CR tab, the UI show "Og, no! Something went wrong." error in the page.
Of course, the operator CR can't be created from the UI. 

We verified this works in OCP 4.7 and OCP 4.8 RC versions.


How reproducible:

Steps to Reproduce:
1. install operator with multiple version in its CRD from operator hub on OCP 4.6
2. switch to the installed operator details page
3. we found that the UI will show multiple tab for the corresponding CR
4. click one of the CR tab, the UI show "Og, no! Something went wrong." error in the page


Actual results:

the UI show "Og, no! Something went wrong." error in the page.
the operator CR can be created from the UI. 

Expected results:

the UI shows only the latest version of CR in the tab, one tab for CR only, see behavior of OCP 4.7 and OCP 4.8
the operator CR can be created from the UI.

Comment 1 W. Trevor King 2021-07-08 03:49:47 UTC
(In reply to Longlong Cao from comment #0)
> After install operator with multiple version in its CRD from operator hub on
> OCP 4.6, then switch to the installed operator details page, we found that
> the UI will show multiple tab for the corresponding CR.
> If we click one of the CR tab, the UI show "Og, no! Something went wrong."

Sounds like a (dev?) console issue?  Possibly an API issue?  Seems very unlikely to be a cluster-version operator issue.

Comment 2 Longlong Cao 2021-07-15 11:55:09 UTC
Yes, looks like the issue is UI/Console issue, the CSV support multiple-versions CRD.

Comment 3 Bryan Florkiewicz 2021-07-23 19:28:34 UTC
PR reviewed. Waiting on cherry-pick-approved label/group lead approval

Comment 5 Yanping Zhang 2021-07-26 03:42:06 UTC
Checked on ocp 4.6 cluster with payload 4.6.0-0.nightly-2021-07-23-235448.
Install Advanced Cluster Management for Kubernetes Operator, check on the installed operator details page, click the CR tabs, there is no error.
The bug is fixed.

Comment 8 errata-xmlrpc 2021-08-04 19:59: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 (OpenShift Container Platform 4.6.41 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/RHBA-2021:2886


Note You need to log in before you can comment on or make changes to this bug.