Bug 2019301 - Service binding created outside topology is not visible
Summary: Service binding created outside topology is not visible
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.8.z
Assignee: Mohammed Saud
QA Contact: spathak@redhat.com
URL:
Whiteboard:
Depends On: 2017484
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-02 06:51 UTC by Mohammed Saud
Modified: 2022-02-21 20:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
* Before this update, the service binding connector did not appear in topology if you used a `resource` property instead of a `kind` property to define a `ServiceBinding` custom resource (CR). This update resolves the issue by reading the CR's `resource` property to display the connector on the topology. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2013545[BZ#2013545])
Clone Of: 2017484
Environment:
Last Closed: 2022-02-16 06:51:40 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10376 0 None open [release-4.8] Bug 2019301: Check for resource in ServiceBinding spec's service reference 2021-11-09 06:52:45 UTC
Red Hat Product Errata RHBA-2022:0484 0 None None None 2022-02-16 06:51:59 UTC

Comment 5 spathak@redhat.com 2022-02-11 06:24:17 UTC 
Verified on build version: 4.8.0-0.nightly-2022-02-08-181141
Browser: Google Chrome 98
Comment 7 errata-xmlrpc 2022-02-16 06:51:40 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 (OpenShift Container Platform 4.8.31 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.

https://access.redhat.com/errata/RHBA-2022:0484
Note You need to log in before you can comment on or make changes to this bug.