Bug 1668200
Summary: | Search Gateway: "Unknown resource: gatewaies/networking.istio.io/v1alpha3" | ||||||
---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Javier Ramirez <javier.ramirez> | ||||
Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.10.0 | CC: | aos-bugs, jokerman, mmccomas, spadgett, yanpzhan | ||||
Target Milestone: | --- | ||||||
Target Release: | 4.1.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Previously, listing Istio Gateway resources in the web console Other Resources view would cause an error. This has been fixed in the 4.0 console, where the Home -> Search view correctly shows the list of Gateway resources.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-06-04 10:42:06 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
Javier Ramirez
2019-01-22 08:05:19 UTC
Ideally we should avoid using kindToResource and just use the resource returned from API discovery. This is fixed in the 4.0 console. registry.svc.ci.openshift.org/openshift/origin-v4.0-2019-01-28-212509@sha256 40c1d5bad78f9f98331a66c8aee098ad93bf295c245bd0501be1c6118c98cadd 40e6659c2417 12 hours ago 269 MB console repo commit id: 3c3e54803fa9a223b1f4e817cc2c710e000414df Checked on Search page, not all the resources items have apiversion added in dropdown list, pls refer to attachment. Created attachment 1524469 [details]
searchlist
This is expected. We only show api group when the same resource appears in more than one api group to avoid clutter. According to Comment 5 and Comment 7, the bug has been fixed, now only show api group when the same resource appears in more than one api group. 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, 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-2019:0758 |