[ODLPARENT-122] ODL is slow to connect to netconf testtool in -all- jobs Created: 26/Sep/17  Updated: 22/Aug/19  Resolved: 22/Aug/19

Status: Resolved
Project: odlparent
Component/s: General
Affects Version/s: 3.0.2
Fix Version/s: 5.0.0

Type: Bug
Reporter: Vratko Polak Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 9212

 Description   

I thought there already is a Bug for this, but I cannot find it.

This is similar to ODLPARENT-112 but this time it is not clear whether it is the testtool being slow to accept the connection, or ODL netconf connector is slow to initiate it.

Either way this is influencing CSIT results, when a segment of a suite occasionally fails [0], because the device is still shown as "connecting" in operational netconf-topology.

[0] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-1node-userfeatures-all-nitrogen/162/log.html.gz#s1-s4-s1-t5-k2-k1-k1-k2

 Comments   
Comment by Tomas Cere [ 04/Oct/17 ]

Since testtool uses the same ssh implementation as the rest of netconf this is likely related to the regression from the karaf4 upgrade

Comment by Andrej Vanko [ 09/Oct/17 ]

Since testtool uses the same ssh implementation as the rest of netconf this is likely related to the regression from the karaf4 upgrade
moved to odlparent

Comment by Robert Varga [ 22/Aug/19 ]

The implementation has shifted version, I do believe this cannot be reproduced now.

Generated at Wed Feb 07 20:27:41 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.