Ricardo Carrillo Cruz a56de25df5 Fix persistent command timeout handling (#34791) ... * Fix persistent command timeout handling We were using play context timeout on ansible-connect to set the persistent command timeout handler. Thus, we were ignoring the persistent_command_timeout setting. Moreover, even by changing that on ansible-connection, were again overriding it on cliconf send_command, since in a same process we can just set a single alarm and cliconf send_command alarm setup is executed after ansible-connection alarm setup. * Remove alarm setting on cliconf send_command The alarm is set regardless before it is executed by ansible-connection. Setting an alarm again, overrides/disables the previous ones as a single process can just have a single alarm set. * Move the setting of persistent command timeout to network_cli We do also use ansible-connection for connection local, so if a user provides a timeout via provider that would be ignored if we set the value on ansible-connection. Moving that logic to network_cli plugin constructor makes both connections to work. * Remove debug statements * Set the persistent command timeout on task_executor We can't set the timeout on ansible-connection nor network_cli, otherwise tasks using provider timeout won't work.		2018-01-13 15:54:44 +01:00
..
ansible	Fix persistent command timeout handling (#34791)	2018-01-13 15:54:44 +01:00