No Job output on any Template launch

[janviudapi]

ISSUE TYPE

• Bug Report

SUMMARY

Any template/job I launch there is no output on newly deployed Ansible AWX

There is no job output in http:///#/jobs/playbook/<job_id>/output
Empty job events in https:///api/v2/jobs/<job_id>/job_events/

ENVIRONMENT

AWX version: 17.0.1
AWX install method: Docker containers
Ansible version: 2.9.17
Operating System: Ubuntu 20
Web Browser: Edge and chrome (latest)

STEPS TO REPRODUCE

Launch any Job or template, but no output.

EXPECTED RESULTS

ACTUAL RESULTS

Must be able to see output whether it is failed or success, but since there is no output not able to determine what is going wrong.

ADDITIONAL INFORMATION

I freshly deployed AWX instance

ansible --version
ansible 2.10.5
config file = None
configured module search path = ['/home/vjanvi/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.8/dist-packages/ansible
executable location = /usr/local/bin/ansible
python version = 3.8.5 (default, Jul 28 2020, 12:59:40) [GCC 9.3.0]

docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f9f1517879a5 ansible/awx:17.0.1 "/usr/bin/tini -- /u…" 2 days ago Up 14 hours 8052/tcp awx_task
a90161753531 ansible/awx:17.0.1 "/usr/bin/tini -- /b…" 2 days ago Up 14 hours 0.0.0.0:80->8052/tcp awx_web
65a486047d8e postgres:12 "docker-entrypoint.s…" 2 days ago Up 14 hours 5432/tcp awx_postgres
d7cc1340c825 redis "docker-entrypoint.s…" 2 days ago Up 14 hours 6379/tcp awx_redis

awx_task continer
cd /var/lib/awx
bash-4.4# ls
rsyslog vendor venv

Please let me know Estimated time to resolve this, and which AWX version is stable one so I can use it.

[DanyD]

As a hotfix I figured out you can switch to the details tab and back to output which forces a reload and then shows the log. Seems to be a JS issue not triggering a periodic update.

[dimovstanimir]

The same issue here. There is no update in the template output until the playbook has finished. I only get updates if I refresh manually the page in the browser by hitting F5 every 1-2 seconds or I wait till the template has finished and it dumps all the information regarding the status of the template execution at once.

My configuration is the same as the poster of this bug:

AWX version: 17.0.1
AWX install method: Docker containers
Ansible version: 2.9.17
Operating System: Ubuntu 20.04 LTS
Web Browser: Chrome, Firefox, Edge. All are latest.

I also created an issue for AWX version 16.0.0 ( #8994 ) and was waiting and hoping that in the new release this would be fixed but in the end it seems that this is not the case. By the way is there anyone who hasn't face this issue? It does not seem to be possible just for "some" people after all we are all using the same setup/installation process.

Is this really so hard to be fixed in all versions till now. I think that this is a major bug which require maximum attention and efforts to be fixed as it is quite annoying and stand in the way of a really important functionality.

[janviudapi]

Jut to update, I tried with your fix but still there Output window is Empty #9242

[jakemcdermott]

👋 hello

Thanks for creating this issue.

The job output update bug you described is caused by a combination of #8596 and possibly #9085.

We'll have a fix for it in the upcoming awx release: #9208 (comment)

I'm closing this issue for now - we're tracking the work for this in the issues linked above.

also see:

• AWX 17.0.1 Output is only shown when reloading the page #9193
• Job Output / Time Elapsed not updating until the job finishes #8930
• Can't see stdout output of a job #8973
• Job output not being updated in awx 16.0.0 #9105
• Job output not updating (requires page refresh)  #9112
• Job output not displayed while running - AWX 17.0.0 #9183

[jakemcdermott]

Please let me know Estimated time to resolve this, and which AWX version is stable one so I can use it.

The ETA is: When it's done.

[dimovstanimir]

In version 17.1.0 the job output does not still update automatically but requires manual refresh.

Is this really so hard to be fixed?

[kuznetsovkk]

Is it fixed in 18.0.0?

[lorenzgith]

Is it fixed in 18.0.0?

Nope