-
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
mitogen 0.2.9, network_cli, Ansible 2.8: Warning: could not recover task_vars #662
Comments
Any update ? |
I have a few other things on my plate but after will look into this. Will follow what's here to repro: #342 |
Discovered I have no way to test this unfortunately :( I don't have access to a GNS3 setup to test against. If there was a way I could connect to something to test I'd be able to debug the issue, but until that happens the ticket will have to stay open until someone else picks it up. Sorry about that. |
May I test code ? |
Certainly! Feel free to check out |
I'm seeing this as well with 0.2.9 and master. Not a big deal for me at the moment because our network stuff is in a separate repo/ansible.cfg. |
This may be fixed by v0.3.21, which includes #1215. |
Hello,
I read that mitogen will not improve playbook time for
network_cli
connection but should not break the run either, it was working on 0.2.8 but now a fatal error appears on 0.2.9with mitogen 0.2.8
with mitogen 0.2.9
#342
2.8.6
No
https://mitogen.networkgenomics.com/ansible_detailed.html#common-problems has
instructions to help figure out the likely cause and how to gather relevant
logs.
network_cli connection
Ubuntu 18.04 WSL, same with a Python-alpine docker image
Cisco catalyst 3850
"none"
200 lines of output around the point of the error, along with a full copy of
any traceback or error text in the log.
version along with output of "ansible-config dump --only-changed".
The text was updated successfully, but these errors were encountered: