You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Timeout parameter used in Config class and RPC operations have different purposes and function at different levels in Ansible.
Timeout in Config class is specifically used for configuration related tasks such as applying configuration changes, roll backs etc. The Purpose of this parameter here is to determine the maximum time ansible will wait for the configuration to be complete. If the configuration operation is not completed within this timeout specified, ansible will consider this task as failed.
On the other hand, timeout in RPC is used for tasks that execute RPC’s on a device such as running operational commands, gathering device facts etc. Here the timeout parameter specifies the maximum time ansible will wait for response from RPC operation. If the device doesn’t respond within the timeout specified, ansible will consider this task as unsuccessful. Thus the main difference lies in their scope and purpose ie, timeout in Config class ensures the tasks are completed within a specified duration where as in RPC operations, this parameter ensures timely responses from the devices.
Config class use timeout whereas all RPC uses rpc_timeout.
We should document this difference in behavior.
The text was updated successfully, but these errors were encountered: