-
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
wait_for_connection gives errors #655
Comments
I can reproduce the issue with any use of As a workaround you can specify |
I have also experienced this issue in relation to the wait_for_connection module. Using @davidklaftenegger suggestion of switching back to linear worked for me, but I would love to see this fixed to be able to use the mitogen_linear strategy everywhere. Using ansible 2.7.0 |
as this is still an issue and I don't know how long it will be, here's a more elaborate explanation of the workaround for everyone finding this bug through google: My example playbook is this:
As this fails with mitogen_linear set as the default strategy in my .ansible.cfg, I will instead write it like this:
This will use mitogen for everything but |
…eset Update services.py for issue#655
I took a look at this today #710 . I fixed the
coming from Mitogen's I'm out of time to look at this today but I hope to finish it tomorrow! |
Should have fixed it here: #710 It passed tests on my side. Let me know if it works for you @davidklaftenegger @mlaurense @ubermug . My tests use Ansible 2.8.8 and I ran stuff on an Ubuntu 18.04 container. I'm gonna add the test block in this ticket description to Mitogen so the error doesn't happen again! |
I integrated the test scenario mentioned in the ticket description into #710 (had to use docker though because testing |
Still getting this issue with
Ansible task:
|
I'm using ansible + mitogen for automated server updates on Ubuntu. I'm using these tasks to check if a reboot is necessary after the apt upgrade task:
This can be manually reproduced by just creating a /var/run/reboot-required file.
I recently updated to the latest ansible (2.8.5) and mitogen (master branch). Previously the wait_for_connection would trigger a warning ([WARNING]: Reset is not implemented for this connection), but now the following error is shown every second, from the moment the reboot is complete:
When disabling mitogen, the playbook runs fine.
The text was updated successfully, but these errors were encountered: