Bug 1907827 - Kn resources are not showing in Topology if triggers has KSVC and IMC as subscriber
Summary: Kn resources are not showing in Topology if triggers has KSVC and IMC as subs...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.z
Assignee: Jaivardhan Kumar
QA Contact: Gajanan More
Harsh Mishra
Depends On: 1906683
TreeView+ depends on / blocked
Reported: 2020-12-15 10:46 UTC by OpenShift BugZilla Robot
Modified: 2021-04-22 10:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the users were not able to see any Knative services and sources on the *Topology* view. This was because the triggers had both a Knative service and an In-Memory Channel as subscribers due to a Null Pointer Exception (NPE). This issue is resolved by fixing the Null Pointer Exception, so that the Knative data model returns proper data and the Knative resources are properly shown on the *Topology* view.
Clone Of:
Last Closed: 2021-02-08 13:50:52 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 7550 0 None closed [release-4.6] Bug 1907827: fixes issue with kn resources if trigger goes to ksvc and IMC from same broker 2021-02-05 18:33:45 UTC
Red Hat Product Errata RHSA-2021:0308 0 None None None 2021-02-08 13:51:10 UTC

Comment 3 Gajanan More 2021-02-02 07:26:06 UTC
I have validated the bugzilla on:
Build: 4.6.0-0.nightly-2021-01-30-211400
Browser: Google Chrome Version 87
Marking this as verified

Comment 5 errata-xmlrpc 2021-02-08 13:50: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 (Important: OpenShift Container Platform 4.6.16 security and bug fix 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.


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