Bug 1908868

Summary: Update empty state message for EventSources and Channels tab
Product: OpenShift Container Platform Reporter: Sahil Budhwar <sbudhwar>
Component: Dev ConsoleAssignee: Sahil Budhwar <sbudhwar>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: low Docs Contact:
Priority: medium    
Version: 4.7CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:46:26 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:

Description Sahil Budhwar 2020-12-17 18:44:41 UTC
Description of problem:
When there are no event sources, brokers, triggers, channels or subscriptions and user visits the Eventing page from Admin perspective, for Event Sources, it shows message Not Found . For Brokers, Triggers and subscriptions, it shows No Brokers/Triggers/Subscriptions found but for Channels, it again shows Not Found . 

Prerequisites (if any, like setup, operators/versions):
Install OpenShift Serverless Operator and create Knative Serving and Knative eventing

Expected results:
We should update the message to  No EventSources found or No eventSources/channels from not found

Reproducibility (Always/Intermittent/Only Once):

Build Details:

Comment 3 Gajanan More 2021-01-05 05:38:35 UTC
I have validated the bug on:

Build: 4.7.0-0.nightly-2020-12-21-131655

Browser: Firefox 80

Marking this bug as done.

Comment 5 errata-xmlrpc 2021-02-24 15:46:26 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.