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

Nomad UI Job Details Not Available When Authoritative Region is Down #12040

Closed
MikaelHashiCorp opened this issue Feb 10, 2022 · 1 comment · Fixed by #12041
Closed

Nomad UI Job Details Not Available When Authoritative Region is Down #12040

MikaelHashiCorp opened this issue Feb 10, 2022 · 1 comment · Fixed by #12041
Assignees
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/core type/bug

Comments

@MikaelHashiCorp
Copy link

Nomad version

v1.2.5

Operating system and Environment details

Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal

Issue

When a Nomad authoritative region goes down, the Nomad UI job details are not available from the non-authoritative region, giving the error:

Server Error:  A server error prevented data from being sent to the client.

Reproduction steps

  1. Create a couple of federated multi-region servers.
  1. Deploy a job in the non-authoritative region.
  2. Shut down Nomad agent in the authoritative region.
  3. Go to the Nomad UI jobs page (http://localhost:4646/ui/jobs) and click on any of the job links.

Expected Result

Job details are displayed.

Actual Result

Server Error:  A server error prevented data from being sent to the client.

Workaround

Access the job details via the Nomad CLI and API:

@jrasell jrasell self-assigned this Feb 10, 2022
@jrasell jrasell added stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/core labels Feb 10, 2022
@jrasell jrasell added this to Needs Triage in Nomad - Community Issues Triage via automation Feb 10, 2022
@jrasell jrasell moved this from Needs Triage to In Progress in Nomad - Community Issues Triage Feb 10, 2022
jrasell added a commit that referenced this issue Feb 10, 2022
Nomad - Community Issues Triage automation moved this from In Progress to Done Feb 11, 2022
jrasell added a commit that referenced this issue Feb 11, 2022
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/core type/bug
Projects
Development

Successfully merging a pull request may close this issue.

2 participants