Job Output / Time Elapsed not updating until the job finishes

[tstahnke2]

ISSUE TYPE

• Bug Report

SUMMARY

When launching jobs, all websockets appear to be working correctly, but only the indicator for the job running appears to update. The time elapsed and the output from the job does not appear until the job has completed.

ENVIRONMENT

• AWX version: 16.0.0
• AWX install method: docker on linux
• Ansible version: 2.9.15
• Operating System: Windows 10
• Web Browser: Chrome/Brave/Firefox/Edge

STEPS TO REPRODUCE

1. launch a template
2. the elapsed time will be 0 until the job finishes
3. no output will appear until the job finishes

EXPECTED RESULTS

The job output/time elapsed should continuously update as the job runs

ACTUAL RESULTS

The job output and time elapsed don't update until the job finishes

ADDITIONAL INFORMATION

Screen shot of job right after launching (while the project SCM is updating)

Screen shot after SCM project has updated and the job has run for a few seconds

Screen shot after the job has finished

Note that event the job finished indicator doesn't show up until I reload the view:

[jakemcdermott]

👋 Hello, @tstahnke2 Thanks for creating this issue.

The elapsed time display issue is being tracked here: #8931

And the job output update bug you described is caused by #8596.

We'll have fixes for both in an upcoming awx release.

[robinduerhager]

Hey, i've got the same problem with AWX 20.0.0.
It seems like awx-web is just doing an api call at the start and the end of the job. No elapsed variables are sent via the websockets. However, i do see real-time stdout Output after adding websocket support to my nginx-proxy-manager. Although, the Job Status and elapsed time does update when the job finishes (probably due to an api request happening after initializing the job and one after the end of the job).

In the image, the highlighted request is the last that happened, a few requests before (the /api/v2/jobs/119/ request) is the one that happened after initializing the job.

Didn't know if i should create a new issue for this, because this one matches perfectly to my problem :).

[ryanmerolle]

@robinduerhager I can confirm I have the same issue with AWX 20.0.0

[matsonfruit]

please reopen. still having this issue on AWX 21.0.0