You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that AWX is open source software provided for free and that I am not entitled to status updates or other assurances.
Summary
The installation is on a k3s single-node machine, awx 19.2.2 provisioned via awx-operator 0.12.0
We have a long running playbook (~35 mins) provisioning more than 30 hosts.
The playbook output (in the WebUI) stops after several minutes. The playbook run seems to continue in the background, but not output is generated any more. I examined the relevant table in the postgres db (main_jobevent_XXXXXXXX_XX), the entries also stop at the same point. As the automation-job-xx is destroyed when the playbook finishes, I can't say for sure that the playbook always runs till the end, but judging from my tests I think so.
When watching the log via 'kubectl logs -f automation-job-xx', the output also almost always stops, but mostly at some later time.
I've the feeling that those stops happen when there is a lot of output in a short timespan. I don't have the insight how the logs are collected, but it seems that something isn't able to keep up with the output speed.
Another playbook (~ 12mins runtime) also truncates the output sometimes, and sometimes it finishes correctly.
AWX version
19.2.2
Installation method
kubernetes
Modifications
no
Ansible version
ansible [core 2.11.3.post0]
Operating system
CentOS 7
Web browser
Firefox
Steps to reproduce
A long running job (>10 minutes) with fast log output
Expected results
Job log output should be complete
Actual results
Job log output is truncated
Additional information
No response
The text was updated successfully, but these errors were encountered:
Please confirm the following
Summary
The installation is on a k3s single-node machine, awx 19.2.2 provisioned via awx-operator 0.12.0
We have a long running playbook (~35 mins) provisioning more than 30 hosts.
The playbook output (in the WebUI) stops after several minutes. The playbook run seems to continue in the background, but not output is generated any more. I examined the relevant table in the postgres db (main_jobevent_XXXXXXXX_XX), the entries also stop at the same point. As the automation-job-xx is destroyed when the playbook finishes, I can't say for sure that the playbook always runs till the end, but judging from my tests I think so.
When watching the log via 'kubectl logs -f automation-job-xx', the output also almost always stops, but mostly at some later time.
I've the feeling that those stops happen when there is a lot of output in a short timespan. I don't have the insight how the logs are collected, but it seems that something isn't able to keep up with the output speed.
Another playbook (~ 12mins runtime) also truncates the output sometimes, and sometimes it finishes correctly.
AWX version
19.2.2
Installation method
kubernetes
Modifications
no
Ansible version
ansible [core 2.11.3.post0]
Operating system
CentOS 7
Web browser
Firefox
Steps to reproduce
A long running job (>10 minutes) with fast log output
Expected results
Job log output should be complete
Actual results
Job log output is truncated
Additional information
No response
The text was updated successfully, but these errors were encountered: