Skip to content

tower/job-poll-state

Lifecycle state of the tower-invoke-curl polling loop on this machine

Lifecycle and forensic state of the tower-invoke-curl polling loop for the current job on this machine.

This parameter is intentionally absent from a clean machine. Its mere existence is a signal that a previous polling cycle did not complete successfully, and the next run of tower-invoke-curl (with polling enabled) will refuse to launch a new Tower job until the operator clears the state or opts into a resume.

Values written by the task:

  • running: A polling loop is currently active on this machine.
  • failure: The polling loop terminated with a mapped failure value, an unexpected status value, or a polling GET HTTP error.
  • max-time-expired: The polling loop hit tower/job-poll-max-wait without observing a terminal status. The Tower job itself may still be running on the AWX / Tower server.

The only path that removes this parameter is a successful poll (success value observed). All non-success terminals leave the param in place so the operator can inspect and reconcile state.

Operator workflows after a non-success terminal:

  • Resume polling on the existing Tower job (use after timeout):

    drpcli machines set param tower/job-poll-resume to true

    re-trigger the stage

  • Start fresh with a new Tower job:

    drpcli machines remove param tower/job-poll-state drpcli machines remove param tower/job-id

    re-trigger the stage

Do not set this parameter manually under normal operation. It is managed by the tower-invoke-curl task.

Objects that Reference tower/job-poll-state

Objects used by tower/job-poll-state

Not used in current content packs