Ansible Automation Platform Jobs Stuck in Pending: Root Cause and Fix
Today I ran into one of those issues that looks complex, but turns out to be beautifully simple. Every job I launched in Ansible Automation Platform (Tower / Controller 4.5) just sat there. No output. No errors. No movement. Just PENDING . And sometimes, silence is the loudest signal. What I Saw Everything looked healthy on the surface: Job templates launched successfully Jobs stayed in PENDING forever No logs, no failures, no hints Execution Environments looked perfectly fine At first, I suspected Ansible itself, playbooks, environments, something deep. But this didn’t feel like a playbook problem. This felt like something wasn’t even starting . The Turning Point When jobs don’t start at all, it’s usually not Ansible… it’s scheduling. So I went one level lower services. That’s when I checked Receptor , the quiet engine behind job execution in AAP 4.x. And there it was: systemctl status receptor ● receptor.service - Receptor Loaded: loaded (/usr/lib/system...