Bug 1826646

Summary: shows alert in eventsources form if knative service is not present in namespace
Product: OpenShift Container Platform Reporter: Jaivardhan Kumar <jakumar>
Component: Dev ConsoleAssignee: Jaivardhan Kumar <jakumar>
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   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:29:58 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
Alert of not having kn service none

Description Jaivardhan Kumar 2020-04-22 08:43:24 UTC 
Description of problem:
In Console EventSources form supports only sink to knative Service and in case of no associated service for that form will be never get enabled and user has not much information apart from form field

Version-Release number of selected component (if applicable): 4.5


How reproducible: Always


Steps to Reproduce:
1. Install Serverless operator and eventing operator
2. create a namespace 
3. go to DevConsole -> Add -> EventSources

Actual results:No alert is shown to user in case of knative service is not there


Expected results: Alert should be shown to user in case of knative service is not there


Additional info:
Comment 3 Gajanan More 2020-04-29 08:42:06 UTC 
I have validated the bugzilla on
Build: 4.5.0-0.nightly-2020-04-29-040854
Browser: Google Chrome Version 81.0.4044.129
Please have a look at the shared screenshot
Marking this as verified
Comment 4 Gajanan More 2020-04-29 08:43:20 UTC 
Created attachment 1682777 [details]
Alert of not having kn service
Comment 5 errata-xmlrpc 2020-07-13 17:29:58 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:2409