[NETCONF-264] Configurable timeouts for ask's in clustered netconf topology. Created: 30/Aug/16  Updated: 15/Mar/19  Resolved: 07/Mar/17

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Tomas Cere Assignee: Miroslav Kovac
Resolution: Done 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: 6581

 Description   

When processing large responses we may hit an ask timeout(f.ex. schema resolution), make these configurable per device.

 Comments   
Comment by Vratko Polak [ 30/Aug/16 ]

The symptom of this Bug is a failure in som CSIT tests.
This happens in all jobs when the device is ODL (config northbound). Example: [0].
The workaround (already applied by the suite) is to delete the device from topology-netconf and try again.
3 tries are usually enough [1], but not always, especially in Beryllium [2].

[0] https://logs.opendaylight.org/releng/jenkins092/bgpcep-csit-3node-periodic-bgpclustering-all-boron/100/archives/log.html.gz#s1-s4-t5-k3-k1-k1-k1-k2-k10-k1-k2-k4-k1
[1] https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-3node-periodic-bgpclustering-all-boron/100/robot/bgpcep-bgpclustering.txt/010%20Singlepeer%20Prefixcount%201Route/Configure_Netconf_Device/
[2] https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-3node-periodic-bgpclustering-all-beryllium/100/robot/bgpcep-bgpclustering.txt/010%20Singlepeer%20Prefixcount%201Route/Configure_Netconf_Device/

Comment by Miroslav Kovac [ 20/Feb/17 ]

https://git.opendaylight.org/gerrit/#/c/51949/

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