Bug 1832280

Summary: Visual connector cannot distinguish between nodes of different kinds
Product: OpenShift Container Platform Reporter: divgupta
Component: Dev ConsoleAssignee: divgupta
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.5CC: aos-bugs, nmukherj, spathak
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:35:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
Visual connector can distinguish between nodes of different kinds none

Description divgupta 2020-05-06 13:01:43 UTC
Description of problem:
The visual connector creates a `connects-to` annotation whose value is a comma separated or JSON array list of `app.kubernetes.io/instance` strings for matching to their target. The problem is that the `instance` is just a name and is not unique amongst resources.

The value of the annotation needs to be able to uniquely identify different resources by kind and name.

How reproducible: Always

Steps to Reproduce:
1. Create different kinds of resources(that are shown in topology) with same name in a project.
2. Try to connect a node with a node whose name is same as some other nodes.
3. Connection is made to other node with the same name as target node.

Actual results:
Connection is made to other node with the same name as target node.

Expected results:
Connection should be made to the target node.

Comment 5 spathak@redhat.com 2020-05-22 13:22:18 UTC
Created attachment 1691059 [details]
Visual connector can distinguish between nodes of different kinds

Comment 6 spathak@redhat.com 2020-05-22 13:55:33 UTC

Verified on build version: 4.5.0-0.ci-2020-05-22-080435
Browser version: Firefox 73

Comment 7 errata-xmlrpc 2020-07-13 17:35: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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.