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.
(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.
Yes, looks like the issue is UI/Console issue, the CSV support multiple-versions CRD.
PR reviewed. Waiting on cherry-pick-approved label/group lead approval
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.
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