Bug 1906683 - 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...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.7.0
Assignee: Jaivardhan Kumar
QA Contact: Karthik Jeeyar
Harsh Mishra
URL:
Whiteboard:
Depends On:
Blocks: 1907827
TreeView+ depends on / blocked
 
Reported: 2020-12-11 06:26 UTC by Jaivardhan Kumar
Modified: 2021-02-24 15:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In case of multiple triggers one subscribing to Knative service and another to In Memory Channel as subscriber, the Knative resources were not displayed on the *Topology* view. This issue has been fixed now, so that the Knative data model returns proper data, and the Knative resources are displayed on the *Topology* view.
Clone Of:
Environment:
Last Closed: 2021-02-24 15:42:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 7519 0 None closed Bug 1906683: fixes issue with kn resources if trigger goes to ksvc and IMC from same broker 2021-02-09 15:34:19 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:42:45 UTC

Description Jaivardhan Kumar 2020-12-11 06:26:11 UTC
Description of problem: Kn resources are not showing in Topology if triggers has KSVC and IMC as subscriber


Version-Release number of selected component (if applicable):Serverless operator 1.11


How reproducible: Always


Steps to Reproduce:
1. Create a KSVC
2. Create a Channel implementation i.e In Memory Channel  IMC 
3. Create a broker
4. Create a PingSource and sink to broker created above
5. Create a trigger subscribing broker to IMC
6. Create a trigger subscribing broker to KSVC

Actual results: Kn resources are not showing in Topology for above scenario


Expected results: Kn resources should show in Topology for above scenario


Additional info:

Comment 3 Karthik Jeeyar 2021-01-11 06:40:43 UTC
verified as kubeadmin on
Build no : 4.7.0-0.nightly-2021-01-10-070949
https://console-openshift-console.apps.dev-svc-4.7-011101.devcluster.openshift.com/topology/ns/karthik?view=graph

Comment 5 errata-xmlrpc 2021-02-24 15:42: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.

https://access.redhat.com/errata/RHSA-2020:5633


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