You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ubuntu 16.04.6 LTS on AWS
Nomad clusters federated between three AWS regions, us-east-1, us-west-2, eu-central-1
Issue
When connected to the Nomad UI with a cluster that is not the selected cluster, stopping a job in the selected cluster stops the job in the cluster local to the UI you are accessing instead.
Request targets the Nomad API local to the UI region without setting the region query param.
Reproduction steps
Access the Nomad UI from a datacenter endpoint (ie., http://nomad.us-east-1/ui/)
Change the region selector to a remote region (ie., eu-central-1)
Pick a job out of the list of running jobs
Click the stop button and confirm
Now the job will be stopped in us-east-1 but noteu-central-1.
Job file (if appropriate)
Stupid-simple job to test with. Deployed to each region.
We are hitting this in 0.10.2 as well.
I believe this was solved in 0.12.1 by @DingoEatingFuzz. Can someone confirm if this is not planned to be backported?
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.
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
Nomad v0.10.1 (0d4e5d9)
Operating system and Environment details
Ubuntu 16.04.6 LTS on AWS
Nomad clusters federated between three AWS regions,
us-east-1
,us-west-2
,eu-central-1
Issue
When connected to the Nomad UI with a cluster that is not the selected cluster, stopping a job in the selected cluster stops the job in the cluster local to the UI you are accessing instead.
Request targets the Nomad API local to the UI region without setting the
region
query param.Reproduction steps
http://nomad.us-east-1/ui/
)eu-central-1
)Now the job will be stopped in
us-east-1
but noteu-central-1
.Job file (if appropriate)
Stupid-simple job to test with. Deployed to each region.
Nomad Client logs (if appropriate)
If possible please post relevant logs in the issue.
Logs and other artifacts may also be sent to: nomad-oss-debug@hashicorp.com
Please link to your Github issue in the email and reference it in the subject
line:
Emails sent to that address are readable by all HashiCorp employees but are not publicly visible.
Nomad Server logs (if appropriate)
The text was updated successfully, but these errors were encountered: