Bug 1833065

Summary: EventSource card on Add should show if knativeEventing Crd is present and have EventSources
Product: OpenShift Container Platform Reporter: Sahil Budhwar <sbudhwar>
Component: Dev ConsoleAssignee: Sahil Budhwar <sbudhwar>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:35:59 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-05-07 18:11:03 UTC
Description of problem:
EventSource card on Add should show if knativeEventing Crd is present and have EventSources.

In serverless operator 1.7 GA (Eventing is part of it) we provide CRDs for knativeEventing and then user can create CR for these i.e if created for knativeEventing then all CRDs for various eventSources are available in cluster , it used to happen default with Eventing Operator earlier just with installation.

Prerequisites (if any, like setup, operators/versions):
Install Serverless operator 1.7.

Steps to Reproduce:
1. Check CRDs can't see any of the sources
2. Go to DevConsole -> Add

Actual results: Can see EventSource Card

Expected results: EventSource Card should be shown only if sources are present and user have proper access (Note : create CRs for KnativeEventing and it'll add CRDs for various sources in cluster)

Reproducibility (Always/Intermittent/Only Once): Always

Comment 3 Gajanan More 2020-05-14 12:08:06 UTC
I have validated the bugzilla on
Build: 4.5.0-0.ci-2020-05-13-231257
Browser: Google Chrome Version 81.0.4044.129
Please have a look at the shared screenshots
Marking this as verified.

Comment 4 errata-xmlrpc 2020-07-13 17:35:59 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.