s1113950
commented
4 years ago Can you try ansible 2.8.8? Ansible 2.9+ isn't fully supported by Mitogen yet
Open rdghickman opened 4 years ago
s1113950
commented
4 years ago Can you try ansible 2.8.8? Ansible 2.9+ isn't fully supported by Mitogen yet
rdghickman
commented
4 years ago Interestingly I tried it on an Ubuntu 18.0.4.4 system (Ansible 2.9.6) and it was fine. I will try and downgrade Ansible on the WSL Debian box though.
rdghickman
commented
4 years ago Also happens with Ansible 2.7.7 on the WSL Debian box. I am having to conclude that either Python or Mitogen doesn't like something about WSL, but I'm not sure what.
s1113950
commented
4 years ago We use Azure Devops for part of our testing, and Travis for the other part. From what I can tell it's not possible to test on a WSL setup in Azure Devops https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops 🤔 . Unfortunately I don't have a Windows system to test on either :/ If it were possible to get something like a WSL2 docker image that could work lol but not sure that's even possible. Hopefully another Mitogen contributor has this system and can take a look at this ticket 🤞
rdghickman
commented
4 years ago I do wonder if something like this is the cause, if it's waiting on the termination of a child process that ends up never happening: https://github.com/microsoft/WSL/issues/3766
anxstj
commented
3 years ago Occasionally I see the same error in our CI environment, but I wasn't able to reproduce it.
...
PLAY RECAP *********************************************************************
linux-debian-10-ci : ok=501 changed=179 unreachable=0 failed=0 skipped=256 rescued=0 ignored=0
linux-debian-10-gl : ok=492 changed=181 unreachable=0 failed=0 skipped=244 rescued=0 ignored=0
linux-debian-9-ci : ok=494 changed=178 unreachable=0 failed=0 skipped=257 rescued=0 ignored=0
ERROR! [mux 774] 10:01:43.881377 E mitogen.[docker.linux-debian-10-gl]: Broker(4e50): pending work still existed 3 seconds after shutdown began. This may be due to a timer that is yet to expire, or a child connection that did not fully shut down.
ERROR! [mux 774] 10:01:46.187997 E mitogen: Broker(65f8): pending work still existed 5 seconds after shutdown began. This may be due to a timer that is yet to expire, or a child connection that did not fully shut down.
--> Scenario: 'test'
--> Action: 'idempotence'
ERROR:
PLAY [all] *********************************************************************
TASK [Gathering Facts] *********************************************************
fatal: [linux-debian-10-ci]: UNREACHABLE! => {"changed": false, "msg": "Connection timed out.", "unreachable": true}
fatal: [linux-debian-10-gl]: UNREACHABLE! => {"changed": false, "msg": "Connection timed out.", "unreachable": true}
ok: [linux-debian-9-ci]
...It's a Debian 10 docker container with Ansible 2.9.17 and mitogen 0.2.9.
Which version of Ansible are you running? 2.9.6 with Python 3.7.3 (also tried with 2.7.16)
Is your version of Ansible patched in any way? No
Are you running with any custom modules, or
module_utilsloaded? NoHave you tried the latest master version from Git? Yes
Mention your host and target OS and versions Debian 10 running on WSL
Mention your host and target Python versions 3.7.3 (and 2.7.16)
Created a very simple ansible playbook such as the following:
Used by a simple playbook:
Running it with strategy
mitogen_linearresults in the execution completing but the following error appearing:ERROR! [mux 16518] 14:47:49.436676 E mitogen.[local.16555]: Broker(1550): pending work still existed 3 seconds after shutdown began. This may be due to a timer that is yet to expire, or a child connection that did not fully shut down.This seems to happen if:
localhostdelegate_tothelocalhostVerbose output: