Bug 1722879

Summary: Type key instead of Kind
Product: OpenShift Container Platform Reporter: Irina Gulina <igulina>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, hasha, jokerman, mmccomas
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:32:19 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 Flags
screenshot for comment #0 none

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