Skip to content
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

Closed
6 of 11 tasks
Klaas- opened this issue Mar 27, 2024 · 11 comments · Fixed by #15043
Closed
6 of 11 tasks

[24.1.0] Job output not loading -- status not updating #15038

Klaas- opened this issue Mar 27, 2024 · 11 comments · Fixed by #15043

Comments

@Klaas-
Copy link
Contributor

Klaas- commented Mar 27, 2024

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that AWX is open source software provided for free and that I might not receive a timely response.
  • I am NOT reporting a (potential) security vulnerability. (These should be emailed to 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

  • UI
  • UI (tech preview)
  • API
  • Docs
  • Collection
  • CLI
  • Other

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

@wiad
Copy link

wiad commented Mar 27, 2024

We also see this after update to 24.1.0, worked in 24.0.0.

@fosterseth
Copy link
Member

might be caused by this https://github.com/ansible/awx/pull/15031/files

@TheRealHaoLiu

@fosterseth fosterseth added high priority needs_investigation PRs or issues that need further investigation and removed needs_triage labels Mar 27, 2024
@donnieelmore
Copy link

We are seeing this after updating 24.1.0 as well.

@tanganellilore
Copy link
Contributor

Same to me !

@TheRealHaoLiu
Copy link
Member

yep... i broke it

@TheRealHaoLiu TheRealHaoLiu self-assigned this Mar 27, 2024
@TheRealHaoLiu
Copy link
Member

#15031... scratching my head about how i broke it...

@TheRealHaoLiu
Copy link
Member

TheRealHaoLiu commented Mar 27, 2024

#15043

@Klaas-
Copy link
Contributor Author

Klaas- commented Apr 11, 2024

Feedback: Works fine again on 24.2.0 -- thanks for the quick fix!

@ranvit
Copy link

ranvit commented May 16, 2024

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

cc @TheRealHaoLiu

@tanganellilore
Copy link
Contributor

Please, add more info like env and o on.
On k8s, check your ingress control if websocket are allowed.
Standard nginx ingress control not have it enabled.

@ranvit
Copy link

ranvit commented May 17, 2024

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:

  • I spent a long time messing with my ALB's attributes, thinking it was a networking issue.
  • I randomly got the logs to live-refresh when I first tried it in Safari, but then couldn't replicate a successful live-refresh.
  • The Job-status badge updates via WebSocket successfully, but the job logs fail to live update. So this tells me my ingress infra is configured to support websockets properly
  • I simulated network throttling and observed the logs live-refresh, BUT it was only a subset of the logs and they were completely out of order. this convinced me even further that its a ui bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment