Bug 1748771

Summary:	some icons of operators loading got 404 error
Product:	OpenShift Container Platform	Reporter:	shahan <hasha>
Component:	Management Console	Assignee:	Alec Merdler <amerdler>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	aos-bugs, jokerman
Target Milestone:	---
Target Release:	4.2.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:	2019-10-16 06:40:12 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 2019-09-04 07:33:32 UTC

Description of problem:
 some icons of operators loading got 404 error.

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-09-03-102130

How reproducible:
Always

Steps to Reproduce:
1.Check OperatorHub page
2.
3.

Actual results:
Some icons of operator disappearing, such as Logging，elasticsearch, descheduler, federation.
icon:1 GET https://console-openshift-console.apps.qe-ui-09040831.qe.devcluster.openshift.com/api/kubernetes/apis/packages.operators.coreos.com/v1/namespaces/openshift-marketplace/packagemanifests/cluster-logging/icon?resourceVersion=cluster-logging.preview.clusterlogging.4.1.13-201908210601 404 (Not Found)

Expected results:
Icons should loading well.

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1744490 It appears this issue different from that bug.

Comment 2 shahan 2019-09-10 02:49:27 UTC

The icons of Logging，elasticsearch, descheduler, federation operators can load well.
4.2.0-0.nightly-2019-09-09-150607

Comment 3 errata-xmlrpc 2019-10-16 06:40:12 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