-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broadcast messages cause cli_command to timeout. #589
Comments
I noticed that this also impacts the cisco.ios.ios_command module. |
Hey @ptoal that is expected as it is unable to identify the required prompt, we can definitely update the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
When executing a command that triggers a broadcast message on Cisco IOS devices, the cli_command module will sometimes fail with a timeout. An example of a command that does this is:
reload in 5
. When executed on a Cisco IOS device, that command will trigger a broadcast message to be issued, eg:ISSUE TYPE
COMPONENT NAME
ansible.netcommon.cli_command
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
Cisco C3560E / IOS: Version 15.0(2)SE11
STEPS TO REPRODUCE
Using the playbook snippet below, it is possible to trigger a timeout every time. By using
ansible_buffer_read_timeout: 2
, we wait for the broadcast message. Without this setting, the command will succeed or fail somewhat randomly, based on whether or not the broadcast message is received by the module in time.EXPECTED RESULTS
A broadcast message by the system should be ignored while processing commands and output, to ensure reliable execution.
ACTUAL RESULTS
When executed, the playbook will fail due to a timeout. I believe this is happening because the module is being confused by the broadcast message.
When the module fails, the output from the ansible_log looks like this:
A successful command (no timeout) does not have
response-8
in the output.The text was updated successfully, but these errors were encountered: