Skip to content

Upstream 2116 - Use the web supervisord config in the web liveness probe - #23

Open
blaipr wants to merge 1 commit into
ctrliq:develfrom
blaipr:fix/web-liveness-supervisord-config
Open

Upstream 2116 - Use the web supervisord config in the web liveness probe#23
blaipr wants to merge 1 commit into
ctrliq:develfrom
blaipr:fix/web-liveness-supervisord-config

Conversation

@blaipr

@blaipr blaipr commented Aug 12, 2026

Copy link
Copy Markdown

Upstream PR: ansible/awx-operator#2116

SUMMARY

The web deployment's liveness probe runs supervisorctl against /etc/supervisord_task.conf:

(exit $(/usr/bin/supervisorctl -c /etc/supervisord_task.conf status | grep -vc RUNNING))

That is the task pod's configuration — the line is byte-identical to the one in task.yaml.j2. The web pod's liveness probe therefore reports on the task process group instead of its own, so a web pod whose own processes have stopped can still pass its liveness check.

Confirmed the target path is valid for the Ascender images: tools/ansible/roles/dockerfile/templates/Dockerfile.j2 in ctrliq/ascender installs supervisor_web.conf to /etc/supervisord_web.conf.

Not present in this fork.

ISSUE TYPE
  • Bug, Docs Fix or other nominal change
COMPONENT NAME
  • Other (installer role templates)

The web deployment's liveness probe invoked supervisorctl against
/etc/supervisord_task.conf, the task pod's configuration, so it reported
on the task process group rather than the web one.

Ports ansible/awx-operator#2116.
@blaipr blaipr changed the title Use the web supervisord config in the web liveness probe Upstream 2116 - Use the web supervisord config in the web liveness probe Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant