Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1609733

Summary:	[admin] resources icons should keep consistent on console
Product:	OpenShift Container Platform	Reporter:	shahan <hasha>
Component:	Management Console	Assignee:	Samuel Padgett <spadgett>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.11.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	3.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-11 07:22:47 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:

Description shahan 2018-07-30 09:59:32 UTC

Description of problem:
 Most of the resource icons are inconsistency across pages.

Version-Release number of selected component (if applicable):
registry.reg-aws.openshift.com:443/openshift3/ose-console             7afc9cdb911ba    

How reproducible:
Always

Steps to Reproduce:
1. create CRD CronTab using default yaml file on admin console
2. check the left resources icons of CronTab on CRD page
3. check the left resources icons of CronTab on search page 
4. also could check 'BundleBinding' crd on CRD & search page

Actual results:
2. It is 'CT'
3. It is 'CRO'
4. It is  'BB' in CRD page, however, it's 'BUN' in search page

Expected results:
They are should keep consistent.

Additional info:

Comment 1 Samuel Padgett 2018-07-30 13:00:14 UTC

Fixed by https://github.com/openshift/console/pull/321

Comment 2 shahan 2018-07-31 06:11:20 UTC

Checked this issue on the latest version admin console, it has been fixed. 
Now the resource icon abbreviation consistently uses the capital letters from a resource name. Verified the bug.
docker.io/openshift/origin-console                                        309e75e44c745       268MB

Comment 4 errata-xmlrpc 2018-10-11 07:22:47 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-2018:2652