-
Notifications
You must be signed in to change notification settings - Fork 199
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
Cisco module not working at all #342
Comments
Thanks for reporting this. I'm still working through Ansible 2.6 issues, and possibly this a new one. Have you tried on 2.5? I have personally never seen network_cli working due to the difficulty in getting a working gns3 config to test against |
I will spin up a new VM and test with Ansible 2.5. This is the first issue I've encountered with 2.6.x so far. Will update this shortly. |
On investigating the stack trace, it seems highly likely that it is broken on 2.5 too -- it is using a private method of the old SSH plugin that the Mitogen replacement lacks. Please leave this with me -- these will be easy to fix once I have a working GNS3 running somewhere to test against |
Confirmed issue with 2.5.0 also: OS info:
Python info:
Ansible info:
Error:
|
network_cli connection type loads the "ssh" (mitogen_ssh) plugin and expects a private method to exist.
This should now be fixed on the master branch and will make it into the next release. To be updated when a new release is made, subscribe to https://www.freelists.org/list/mitogen-announce If you are still experiencing the problem on the current master branch, please do not hesitate to reopen this issue. Thanks for reporting this! |
Hey, thanks for letting me know. I've just downloaded the master branch again and gave it a go. I'm afraid to say, I'm still getting a stack trace error:
Here's some info on my switch incase you were testing with a different IOS version:
If you need any more info from -vvv then let me know |
Thanks a ton for letting me know! I had a worked GNS3 setup not a week ago, and can't get the damn thing to connect today. Wil re-close the bug once I've absolutely confirmed it's working. Sorry for the hassle :) |
Not at all. Bugs are meant to be squished! More than happy to test etc |
The action monkey-patch shouldn't be active at all, zero clue how that code is even running! |
More than happy to send over my playbook for you to experiment if necessary. |
Hi, we are facing up the same problem in our project. Do you already know if that issue is solvable? |
I have tested with the latest release of Mitogen and it seems to be fine for me. Thanks @dw! |
Really, it's fixed? :) That's nice! I struggled to get a working GNS3 setup to test against. Do any of you networking folk know how I can get an easy to maintain GNS3 up and running? I wasted hours messing around, and only managed to keep it working for a single night. Really I want some kind of VM with the telnet server exposed. Any ideas? |
Yeah running my Cisco backup script works fine with the last release! I’ve not used GNS3 personally, but pretty sure they have an ESXi image that you can import, if you use that at all |
Apologies for mail spam, just narrowly avoided a catastrophe! |
11237 - Ecuador (Quito) Mobile - Hosted by Azurreo
Error in the initial report. Ansible 2.6.2, Python 2.7.15, Mitogen unclear.
Error reported in #342 (comment). Ansible, Python, and Mitogen versions unclear.
I think this is https://en.wikipedia.org/wiki/Graphical_Network_Simulator-3
|
This may be fixed by v0.3.21, which includes #1215. |
Hi there,
I am using the Cisco module which works without Mitogen enabled. This is using the current master branch.
OS info:
Ansible info:
Python info:
Ansible group info:
Error:
The text was updated successfully, but these errors were encountered: