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

Exec button in Nomad UI not working from allocation page. #9966

Closed
zhelezovartem opened this issue Feb 4, 2021 · 4 comments · Fixed by #9968
Closed

Exec button in Nomad UI not working from allocation page. #9966

zhelezovartem opened this issue Feb 4, 2021 · 4 comments · Fixed by #9968

Comments

@zhelezovartem
Copy link

Nomad version

Nomad v1.0.2 (4c1d4fc)

Operating system and Environment details

Ubuntu 18.04.5 LTS

Issue

I have ACL-enabled Nomad cluster. Nomad job run in non-default namespace. I go to Nomad UI and authenticate myself with management token. I choose my job, then choose one of running allocations and try to push Exec button on the allocation page. As a result, I got this error:

Not Found
What you're looking for couldn't be found. It either doesn't exist or you are not authorized to see it.

At the same time, if I try to push Exec button from the job page, it works as expected.

@cgbaker
Copy link
Contributor

cgbaker commented Feb 4, 2021

Thanks for the report, @zhelezovartem, I have most recently seen this behavior as well. Based on the queries from the browser, it appears that the UI is neglecting to pass the ?namespace parameter. We'll look into this further.

@zhelezovartem
Copy link
Author

Great, thanks!

@backspace backspace self-assigned this Feb 4, 2021
backspace added a commit that referenced this issue Feb 4, 2021
This closes #9966. It was looking at the query parameters
for the namespace and region, but allocation (and task!)
routes don’t have a namespace query parameter. Since the URL
generator requires the job for all calls, it makes sense to
extract the namespace and region from the job instead.
@backspace
Copy link
Contributor

Thanks again, @zhelezovartem, and for the correct diagnosis, @cgbaker. The URL generator was looking for the namespace in the query parameters of the existing URL, but allocation (and task) routes don’t have a namespace query parameter. I’ve opened #9968 to extract the namespace (and region) from the job instead.

backspace added a commit that referenced this issue Feb 4, 2021
This closes #9966. It was looking at the query parameters
for the namespace and region, but allocation (and task!)
routes don’t have a namespace query parameter. Since the URL
generator requires the job for all calls, it makes sense to
extract the namespace and region from the job instead.
@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 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants