awx ad-hoc command (ping) job stay in running status indefinitely about awx HOT 2 OPEN

thanks for raising this issue. how are you monitoring # of active forks at a time? Are you inferring that based on job stdout, or are you exec-ing into pod and looking at running ansible-playbook PIDs?

what fork value are you setting in the ac-hoc command?

where is this job running (i.e. remote execution node, container group, cluster automation pod, etc).

Are there CPU limits set on the cluster where this is running? How many actual CPU cores is on that k8s worker node?

also this sounds more like an ansible issue, not AWX, and you might gain traction by creating a new thread on forum.ansible.com under Get Help section

from awx.

Hello

I used ps command to count number of ssh connection which should be equal zo number of forks

Yes I am looking for pids

we do not have cpu limit on execution node (where the podman run) and the control node where I have awx installed with pods on k3s single cluster node

How can I check resources limite on k3s ?

ok will raise request to ansible team

Thanks for your support

from awx.