Bug 1777969

Summary: Event sources in topology should be displayed with respective icons
Product: OpenShift Container Platform Reporter: Aritra Roy <ariroy>
Component: Dev ConsoleAssignee: Aritra Roy <ariroy>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1777970 (view as bug list) Environment:
Last Closed: 2020-05-04 11:17:52 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
event source icons not displayed
none
event sourcing icon none

Description Aritra Roy 2019-11-28 20:17:48 UTC 
Created attachment 1640495 [details]
event source icons not displayed

Description of problem:
Event sources in topology should be displayed with respective icons i.e for cronJob Source/Container Source/ApiServer Source/Camel k Source/Kafka Source.

Steps to Reproduce:
1.Create an event source e.g cronJob
refer to doc https://docs.google.com/document/d/1F4zECoLRvaUiigLaogbgYOiD_hB_w5hAtcXGY0MxVc4/edit

Actual results:
1.The event source is displayed with openshift icon

Expected results:
1.The event source should have been displayed with its respective icon e.g cronJob icon for a cronJob source
Comment 2 Ruchir Garg 2020-03-02 06:38:37 UTC 
Bulk assigning all to Gajanan for verification.
Comment 3 Gajanan More 2020-03-03 12:49:56 UTC 
Created attachment 1667189 [details]
event sourcing icon
Comment 4 Gajanan More 2020-03-03 12:51:01 UTC 
I have validated this bug on 
Build: 4.4.0-0.ci-2020-03-03-033811
Browser: Google Chrome Version 78.0.3904.108
Marking this as done
Comment 6 errata-xmlrpc 2020-05-04 11:17:52 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-2020:0581