Bug 1722879 - Type key instead of Kind
Summary: Type key instead of Kind
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.2.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-21 14:51 UTC by Irina Gulina
Modified: 2019-10-16 06:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:32:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot for comment #0 (202.98 KB, image/png)
2019-06-21 14:51 UTC, Irina Gulina 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:32:31 UTC

Description Irina Gulina 2019-06-21 14:51:49 UTC 
Created attachment 1583265 [details]
screenshot for comment #0

Description of problem:
In the console "Kind" attribute is shown as "Type"

Version-Release number of selected component (if applicable):
quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:e6b3e376fd5e0e69d65d12f75e349691e21b155b196618dcbfc3cd9865c343cf

How reproducible:
always

Steps to Reproduce:
Catalog -> Installed Operators -> Pick one Operator -> All Instances tab -> see TYPE column, but it's KIND key in YAML

The screenshot attached
Comment 1 Samuel Padgett 2019-07-03 17:40:31 UTC 
https://github.com/openshift/console/pull/1903
Comment 3 shahan 2019-07-08 07:52:34 UTC 
Now the TYPE column has changed to KIND.
verified this bug.
registry.svc.ci.openshift.org/ocp/4.2-2019-07-08-052647@sha256:432a7353f9133eff713844c7a6f2e50e793b2b0cdddc76bd09e9106985c20270
Comment 4 errata-xmlrpc 2019-10-16 06:32:19 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, 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:2922
Note You need to log in before you can comment on or make changes to this bug.