[UI] Cross-region allocation lifecycle button stop & restart fail with 404

[luhhujbb]

For reporting security vulnerabilities please refer to the website.

If you have a question, prepend your issue with [question] or preferably use the nomad mailing list.

If filing a bug please include the following:

Nomad version

0.10.4

Operating system and Environment details

Ubuntu 18.04

Issue

This is a UI issue. In a multi-region deployment, in an allocation view, when trying to restart an allocation of a different region than the region of nomad server which host the UI you are connected to, the life cycle buttons stop & restart imply call to nomad api which doesn't include the region of allocation.

• development tools show that nomad server return 404, however allocation exists
• UI display a confusing message concerning a bad ACL token

Reproduction steps

Setup a dual region (A & B) cluster, launch a job in region B, go to the UI in region A, in one allocation of your job try to stop or restart.

A "copy as curl" of failed call shows that region is forwarded in data when clicking lifecycle button:

• curl 'https://nomad.prod/v1/client/allocation/uuid_allocation_id/restart
• data send : {"TaskName":"task_name","region":"B"}

Response: 404

Solution

Adding a ?region=B in url according to this https://nomadproject.io/api-docs/#cross-region-requests solve the issue.
ie: curl 'https://nomad.prod/v1/client/allocation/uuid_allocation_id/restart?region=B

Explanation

Confusion between query-string params & body params.

Job file (if appropriate)

Not needed

Nomad Client logs (if appropriate)

Not Needed

[github-actions]

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.