ansible/awx

adhoc jobs block other jobs from being processed in the queue

Open

#14,645 建立於 2023年11月9日

在 GitHub 查看
 (5 留言) (1 反應) (0 負責人)Python (13,071 star) (3,333 fork)batch import
communitygood first issuehelp wantedtype:bug

描述

Please confirm the following

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

Bug Summary

When you submit an adhoc job all other jobs (other adhoc, and job templates) are stuck in a pending state until the running adhoc job completes.

AWX version

23.4.0

Select the relevant components

  • UI
  • UI (tech preview)
  • API
  • Docs
  • Collection
  • CLI
  • Other

Installation method

kubernetes

Modifications

no

Ansible version

No response

Operating system

No response

Web browser

Firefox

Steps to reproduce

  1. submit any adhoc job (I used a shell command sleep 30; whoami)
  2. submit a job from "Templates"
  3. observe the job queue

Expected results

all jobs in the unified job queue should process according to capacity. I expect to see more than one job in a running state.

Actual results

The adhoc job is in a running state. All other jobs are stuck in pending waiting for the adhoc command to finish.

Additional information

I am using a container group to run jobs. Capacity of the managed nodes have been visually verified to be < 25% cpu and mem usage. I tried creating a duplicate container group for job templates, which still was stuck in pending, but now with a message waiting for adhoccommand-371 to finish

貢獻者指南

技術棧
pythondockerkubernetes
領域
backenddevops
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
PythonAWX internalsKubernetes basicsConcurrency concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
Investigate the job queue scheduling logic in AWX, specifically how adhoc jobs are assigned to container groups. Look at the task manager code (likely in awx/main/dispatch/ or awx/main/tasks/) and the logic that transitions jobs from pending to running. The issue notes that all other jobs are stuck pending until the adhoc job finishes, suggesting a locking or capacity issue. Review the comments on the issue (#14645) for any additional insights and check the relevant test files for similar scenarios.