-
Notifications
You must be signed in to change notification settings - Fork 19
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
Timeout while running arubaoss_command #25
Comments
hi @LedaxPia this is due to Ansible unable to match on the prompt you specified. Ansible uses regex to match what you provide as a prompt to what's being shown via the switch CLI. To make sure it matches correctly here is the proper
alternatively this also works:
I use this site to practice my regex expressions on, ensure that the "Python" language is selected on the left side! Please try that again and see if your issue is resolved with the proper regex prompt! |
Hey,
With the second regex (.*[y/n]?) I came to the same problem: Rolling out the new config on the switch is working fine but Ansible still gives me the same timeout-error. :/ |
Did you try using single quotations ' instead of the double " the syntax error seems to be an interpretation/formatting issue |
Hey there!
I ran into another issue while running my Playbook.
The Playbook is looking like this:
The output file of the playbook looks like this even though the switch successfully gets the command and reboots during the 120 seconds:
and the output of ansible:
{"changed": false, "stdout": ["timeout value 120 seconds reached while trying to send command: copy tftp startup-config 172.16.XX.XXX orig.cfg"], "stdout_lines": [["timeout value 120 seconds reached while trying to send command: copy tftp startup-config 172.16.XX.XXX orig.cfg"]]}
Some more information:
CentOS 7 with ansible 2.9.27 and Python 3.6.8
Aruba 2530 8G PoE+-Switches with YA.16.10.0016
ansible.cfg:
Inventory:
Thanks for looking into this!
The text was updated successfully, but these errors were encountered: