-
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
Exec button in Nomad UI not working from allocation page. #9966
Comments
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 |
Great, thanks! |
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.
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. |
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.
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. |
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:At the same time, if I try to push
Exec
button from the job page, it works as expected.The text was updated successfully, but these errors were encountered: