Why do Defunct SSH Processes Remain after an Ansible Playbook Run with SSH Password Authentication?

Solution In Progress - Updated -

Issue

After running a playbook with a large fork count and SSH password authentication, defunct SSH child processes remain on the control host.

Environment

Ansible Engine

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In