Bug 2024665 - Bindable services are not shown on topology
Summary: Bindable services are not shown on topology
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Mohammed Saud
QA Contact: Debsmita Santra
Depends On:
TreeView+ depends on / blocked
Reported: 2021-11-18 16:02 UTC by Mohammed Saud
Modified: 2022-03-10 16:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:29:22 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10509 0 None open Bug 2024665: Fix k8sget import for bindable services fetch util 2021-11-18 16:08:40 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:29:38 UTC

Description Mohammed Saud 2021-11-18 16:02:14 UTC
Description of problem:
Bindable services are not showing up on topology and browser console shows the error: `Error fetching bindable services TypeError: Object(...) is not a function`

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

How reproducible:

Steps to Reproduce:
1. Install Service Binding Operator
2. Create BindableKinds CR, add any resource as bindable
3. Navigate to topology

Actual results:
The bindable resource is not shown in topology in a trapezoid shape.

Expected results:
Bindable resource should be visible.

Comment 3 Debsmita Santra 2021-12-08 11:45:30 UTC
can see bindable resources in trapezoid shape

verified on 4.10.0-0.nightly-2021-12-06-201335

Comment 7 errata-xmlrpc 2022-03-10 16:29:22 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.10.3 security 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.