Bug 1810066 - Topology: Visual connector action 'Move connector' doesn't move the connector
Summary: Topology: Visual connector action 'Move connector' doesn't move the connector
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.5.0
Assignee: Jeff Phillips
QA Contact: Ruchir Garg
URL:
Whiteboard:
Depends On:
Blocks: 1810494
TreeView+ depends on / blocked
 
Reported: 2020-03-04 14:06 UTC by Jeff Phillips
Modified: 2020-07-13 17:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1810494 (view as bug list)
Environment:
Version: 4.4.0-0.ci-2020-03-03-215357 Cluster ID: 45266d8f-ab38-42f3-8662-0ef376aaa611 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
Last Closed: 2020-07-13 17:18:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Verification of bug 1810066 on 4.5 release (5.61 MB, image/gif)
2020-03-06 09:09 UTC, Abhishek K N
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4626 0 None closed Bug 1810066: Fix to not allow attempts to move connector to existing targets 2020-06-23 08:59:20 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:18:34 UTC

Description Jeff Phillips 2020-03-04 14:06:18 UTC
Description of problem:

In Topology, Visual connector action 'Move connector' doesn't move the connector.


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


How reproducible:

when selecting a target that is already connected

Steps to Reproduce:
1. Create three nodes (for e.g N1, N2 & N3) in Topology
2. Create a Visual connectors from one node (N1) as source to other two nodes (N2 & N3)
3. Select any connector (for e.g N1 - N2)
4. In side panel, select Action 'Move connector'
5. Select other (N3)

Actual results:

Connector between N1-N2 still exists after Move connector action selection.

Expected results:

Existing targets (other than the current target for the edge) should not be listed as a target for the move. If no other targets are available, the 'Move Connector' action should be disabled.

Additional info:

Comment 3 Abhishek K N 2020-03-06 09:09:35 UTC
Created attachment 1668025 [details]
Verification of bug 1810066 on 4.5 release

Comment 4 Abhishek K N 2020-03-06 09:10:41 UTC
'Move connector' action is inactive if Connects-to relationship is already present between the source and the new target node (PSA).

Verified build: 4.5.0-0.ci-2020-03-05-232742
Verified browsers: Verified Browsers: Chrome Version 80.0.3987.122, Safari Version 13.0.5 (14608.5.12)

Comment 6 errata-xmlrpc 2020-07-13 17:18:09 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.

https://access.redhat.com/errata/RHBA-2020:2409


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