-
Notifications
You must be signed in to change notification settings - Fork 2k
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
ui: Jobs list doesn’t show a new job (on a locally-built binary?) #10555
Comments
@backspace, I was going to make my own issue until I saw this. I am on Amazon Linux 2 with the Nomad version below, and we recently started using two head nodes instead of one. What I have found is that I need to refresh the page for new jobs to show up, which wasn't necessary for a single head node. I hope this gets resolved soon.
|
Adding to this - I updated Nomad from With 3 servers, and an auto-scaled number of clients (Ubuntu 18.04 AMD64), the Jobs UI does not refresh automatically any longer. I have to refresh the browser. I'm not sure if this is Chrome-specific, perhaps when you leave the page it stops long-lived HTTP requests: I can see here that job requests seem to get cancelled. I usually keep the tab open forever-ish and check back occasionally. |
I'm also seeing this locally, where it definitely wasn't an issue before. It makes debugging issues quite a bit more annoying as I typically have 5-6 tabs open as I trigger various actions in Nomad. |
Fixed as part of #20452 |
Nomad version
Operating system and Environment details
macOS 10.14.6
Issue
When viewing the Nomad UI at
localhost:4646
on a locally-built binary, the jobs list doesn’t show a job newly submitted elsewhere. It’s not happening with a released binary 🤔Reproduction steps
Build a Nomad binary that includes the UI with
make dev-ui
, run it, open the jobs list atlocalhost:4646/ui/jobs
, submit a job via CLI.Expected Result
The job should appear in the jobs list.
Actual Result
The job only appears upon refresh, or by leaving and returning to the jobs list.
The text was updated successfully, but these errors were encountered: