Bug 1835332 - After kafka source creation pod is not showing up
Summary: After kafka source creation pod is not showing up
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.5.0
Assignee: divgupta
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-13 15:52 UTC by divgupta
Modified: 2020-07-13 17:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:38:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5430 0 None closed Bug 1835332: Fix kafka source values and validations 2020-08-10 19:46:49 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:38:44 UTC

Description divgupta 2020-05-13 15:52:30 UTC
Description of problem:
After creating kafka source pod is not showing up due to incorrect initial net values in kafka source.

How reproducible: Always

Steps to Reproduce:
1. GO to DevConsole -> Add -> EventSource -> Kafka
2. Add bootStrapServer, knative-topic, consumer-group. Do not add sasl and tls values.
3. Create

Actual results:
Pod not showing up

Expected results:
Pod should show up

Comment 3 Gajanan More 2020-05-26 08:39:05 UTC
I have validated the bugzilla on
Build: 4.5.0-0.nightly-2020-05-25-232952
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified

Comment 4 errata-xmlrpc 2020-07-13 17:38:33 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


Note You need to log in before you can comment on or make changes to this bug.