Netmiko 4.X has deprecated the use of delay_factor in favor of read_timeout, it's still supported, but connection object must be initialized with delay_factor_compat=True, which is set by default to False.
pytntc doesn't set that argument, so netmiko falls back to read_timeout which default is set to 10, regardless of delay_factor setting.
Environment
Python version: 3.8
pyntc version: 1.0.1
Expected Behavior
install_os() command delay can be controlled with with function argument.
Observed Behavior
delay_factor is not respected in netmiko 4.X when delay_factor_compat=True is not set in the connection object.
Steps to Reproduce
Run install_os for cisco_ios, after 10 sec netmiko.exceptions.ReadTimeout is raised regardless of delay factor.
Describe issue
Netmiko 4.X has deprecated the use of
delay_factor
in favor ofread_timeout
, it's still supported, but connection object must be initialized withdelay_factor_compat=True
, which is set by default toFalse
.pytntc
doesn't set that argument, so netmiko falls back toread_timeout
which default is set to10
, regardless ofdelay_factor
setting.Environment
Expected Behavior
install_os()
command delay can be controlled with with function argument.Observed Behavior
delay_factor
is not respected in netmiko 4.X whendelay_factor_compat=True
is not set in the connection object.Steps to Reproduce
Run
install_os
for cisco_ios, after 10 secnetmiko.exceptions.ReadTimeout
is raised regardless of delay factor.