awx ad-hoc command (ping) job stay in running status indefinitely

[bskou57]

Please confirm the following

• [X] I agree to follow this project's code of conduct.
• [X] I have checked the current issues for duplicates.
• [X] I understand that AWX is open source software provided for free and that I might not receive a timely response.
• [X] I am NOT reporting a (potential) security vulnerability. (These should be emailed to [email protected] instead.)

Bug Summary

Hi

I run ping ad-hoc command via awx web interface with high fork

At the beginning it is running faster and finally stay in running state with forking processes 2 by 2 only

why is forking value/capacity decrease over the processing time ?

Thanks for your support

AWX version

23.5.0

Select the relevant components

• [ ] UI
• [ ] UI (tech preview)
• [x] API
• [ ] Docs
• [ ] Collection
• [ ] CLI
• [ ] Other

Installation method

kubernetes

Modifications

no

Ansible version

2.14.2

Operating system

Redhat 8.8

Web browser

Chrome

Steps to reproduce

run awx adhoc command (ping module for example) via inventory on big server list (over 4000) and never finished Note that I have the same behavior with command module

Expected results

job completed in failed or successful status but stay in running status indefinitely.

Actual results

adhoc (ping module) command job is running indefinitely

Additional information

Nothing to highlight in pods logs or podman logs