-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[24.1.0] Job output not loading -- status not updating #15038
Comments
We also see this after update to 24.1.0, worked in 24.0.0. |
might be caused by this https://github.com/ansible/awx/pull/15031/files |
We are seeing this after updating 24.1.0 as well. |
Same to me ! |
yep... i broke it |
#15031... scratching my head about how i broke it... |
Feedback: Works fine again on 24.2.0 -- thanks for the quick fix! |
Feedback: Does not work on v24.3.1 I specifically upgraded from 24.1.0 expecting to pull in this fix, but the Demo Job Template still doesn't follow the logs |
Please, add more info like env and o on. |
Sorry I know that wasn't helpful. I've spent all day looking into it and I'm convinced that the issue I'm experiencing is a ui bug. I'll check back in with more logs when I have a sec, but very briefly:
|
Please confirm the following
security@ansible.com
instead.)Bug Summary
Hi,
it seems with the latest release 24.1.0 there is a regression that job output loading and status updates are no longer happening in firefox/edge.
Reloading whole page works, but then it will also not receive subsequent new output/status updates.
I also looked in ui_next, it has the same problem
AWX version
24.1.0
Select the relevant components
Installation method
kubernetes
Modifications
no
Ansible version
awx-ee 24.1.0
Operating system
No response
Web browser
Firefox, Edge
Steps to reproduce
Start a job, wait for output, nothing happens, reload page see progress, but also no new updates happening
Expected results
Output and status updates become visible automatically
Actual results
Nothing
Additional information
Worked on 24.0.0
The text was updated successfully, but these errors were encountered: