Repository navigation
ansible ansible-playbook crashing with exception #407
Description
Activity
I think this is being caused by whatever version of ansible collections you have installed in
/root/.ansible/collectionsfrom the stack trace. That file is already shipped as part of ansible, i.e./opt/local/lib/python3.13/site-packages/ansible_collections/community/general/plugins/callback/yaml.py. Could you try removing it?Ah, that came to bite me. Well that solved one issue, onto a newer one. I've attempted targeting multiple target OSes (native zone, OpenBSD, Linux) and am getting this error
ansible-playbook -vvv example.ssh.sshd_configs --check --limit example.com ansible-playbook [core 2.19.3] config file = /opt/local/etc/ansible/ansible.cfg configured module search path = ['/etc/ansible/modules'] ansible python module location = /opt/local/lib/python3.13/site-packages/ansible ansible collection location = /root/.ansible/collections executable location = /opt/local/bin/ansible-playbook python version = 3.13.9 (main, Nov 6 2025, 19:59:12) [GCC 13.3.0] (/opt/local/bin/python3.13) jinja version = 3.1.6 pyyaml version = 6.0.3 (without libyaml) Using /opt/local/etc/ansible/ansible.cfg as config file host_list declined parsing /opt/local/etc/ansible/hosts.yml as it did not pass its verify_file() method Parsed /opt/local/etc/ansible/hosts.yml inventory source with yaml plugin running playbook inside collection example.ssh redirecting (type: callback) ansible.builtin.yaml to community.general.yaml Skipping callback 'default', as we already have a stdout callback. Skipping callback 'minimal', as we already have a stdout callback. Skipping callback 'oneline', as we already have a stdout callback. PLAYBOOK: sshd_configs.yaml *********************************************************************************************************************************************************************************************************** 1 plays in /root/.ansible/collections/ansible_collections/example/ssh/playbooks/sshd_configs.yaml PLAY [example] *********************************************************************************************************************************************************************************************************************** TASK [Gathering Facts] **************************************************************************************************************************************************************************************************************** task path: /root/.ansible/collections/ansible_collections/example/ssh/playbooks/sshd_configs.yaml:2 <example.com> Attempting python interpreter discovery. <example.com> ESTABLISH SSH CONNECTION FOR USER: root <example.com> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=30m -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=10 -o 'ControlPath="/root/.ansible/cp/724f31b55d"' -o NumberOfPasswordPrompts=1 example.com '/bin/sh -c '"'"'echo FOUND; command -v '"'"'"'"'"'"'"'"'python3.13'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python3.12'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python3.11'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python3.10'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python3.9'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python3.8'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'/usr/bin/python3'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python3'"'"'"'"'"'"'"'"'; echo ENDFOUND && sleep 0'"'"'' [ERROR]: A worker was found in a dead stateI spent some time poking through some searches on this issue, and it is not yet clear to me why this one is appearing
Thought I'd mention the issue is still persisting after the latest updates to trunk. I may create a new zone for now on older quarterly branch since my SSL certs are about to expire :)
- added a commit that references this issue
on May 6, 2026 - added 9 commits that reference this issue
on May 14, 2026 - added a commit that references this issue
on May 19, 2026 - added 2 commits that reference this issue
on May 22, 2026 - added a commit that references this issue
on Jun 1, 2026
When I run
ansible-playbookwith the latest builds, I get this traceback: