Skip to content
← Back to activity

Solution skill

Unhandled exception during os.killpg

Version 2Sign in to save

Complete solution

Shows how to fix unhandled exception during os.killpg. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

For "debugger: on_failed": upgrade ansible-core past the version containing that fix and the crash goes away. Check your version of Ansible first , maintainers often fix the underlying bug in a later release, and the thread may predate it.

debugger: on_failed

Steps

  1. The PermissionError / os.killpg traceback that surfaces as 'Unexpected Exception, this is probably a bug' was resolved by PR #85907 in ansible-core. Upgrade ansible-core past the version containing that fix and the crash goes away.
  2. This comes from one real issue thread (https://github.com/ansible/ansible/issues/85897); it is the verified fix or approach from that thread, not a general manual. Check your version of Ansible first , maintainers often fix the underlying bug in a later release, and the thread may predate it.

When to use

You are seeing this: Issue ansible/ansible#85897 (closed, 14 comments): ### Summary I've been working on this for days! Use this skill when you run into "Unhandled exception during os.killpg".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Variants

Other phrasings of the same problem that show up in reports:

debugger: on\_failed

``` debugger: on_failed ```

Why this happens

Issue ansible/ansible#85897 (closed, 14 comments): ### Summary I've been working on this for days!

Sources

  • https://github.com/ansible/ansible/issues/85897

Evidence

Issue gh:ansible/ansible#85897 asked: Issue ansible/ansible#85897 (closed, 14 comments): ### Summary I've been working on this for days! I have a playbook calling on a common role and within the role there is a playbook called addgroups.yml. It says the gid of a list of items in a dictionary the gid is undefined! I turned on: ``` debugger: onfailed ``` It's running on MacOS with Homebrew and I ran Disk Utility and there's nothing wrong with the disk! I even reinstalled Ansible and all of it's dependencies! I've run it on the local machine, another machine and a remote machine over the VPN and it gets the same error! I even ran it with a debug module of the dictionary and it stil The verified answer from the thread: The PermissionError / os.killpg traceback that surfaces as 'Unexpected Exception, this is probably a bug' was resolved by PR #85907 in ansible-core. Upgrade ansible-core past the version containing that fix and the crash goes away. Source: https://github.com/ansible/ansible/issues/85897

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_AZJyTNUpmwXM7qAP8bOcxA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Unhandled exception during os.killpg <span>— Vectle</span></a>