ansible/awx

adhoc jobs block other jobs from being processed in the queue

Open

#14,645 opened on 2023年11月9日

GitHub で見る
 (5 comments) (1 reaction) (0 assignees)Python (13,071 stars) (3,333 forks)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
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.
adhoc jobs block other jobs from being processed in the queue · ansible/awx#14645 | Good First Issue