[NETCONF-125] connection-timeout-milliseconds parameter is not working properly for ssh connections Created: 13/Jan/16 Updated: 12/May/21 Resolved: 16/Mar/20 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | Magnesium SR1, Aluminium, Sodium SR3 |
| Type: | Bug | ||
| Reporter: | Jakub Morvay | Assignee: | Sarguna Dharani |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4954 |
| Description |
|
Netconf should timeout connection that is not established after specified time in connection-timeout-millis and then should try to reconnect connection according to reconnecting strategy (obeying other connection parameters like max-connection-attempts etc.) Now, if netconf tries to connect to a device that does not adverties hello message, netconf tiemouts after the specified time but does not cancel established SSH session and immediately tries to establish new connection, ignoring delays between connections and maximum connection attempts. If netconf tries to establish ssh session with device with slow ssh server implementation (simulated by TCP server), it does not timeout after specified time at all. |
| Comments |
| Comment by Jamo Luhrsen [ 20/May/20 ] |
|
rovarga, when I see a ticket like this that was marked 'in review' -> 'resolved' but don't see any gerrit or comment to understand |