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

Forward jobs from Region A to Region B not working #1194

Closed
dverbeek84 opened this issue May 22, 2016 · 1 comment
Closed

Forward jobs from Region A to Region B not working #1194

dverbeek84 opened this issue May 22, 2016 · 1 comment

Comments

@dverbeek84
Copy link

dverbeek84 commented May 22, 2016

Nomad version

Nomad v0.3.2

Operating system and Environment details

CentOS 7

2x nomad servers (region a/b)
2x nomad agents (region a/b)

nomad server-members:

master1.a  172.16.1.11  4648  alive   true    2         0.3.2  a1      a
master1.b  172.16.2.11  4648  alive   true    2         0.3.2  b1      b

nomad node-status:

10819a0a  a  node1.a development  false  ready

nomad node-status:

b7b0d927  a  node1.b development  false  ready

Issue

If i create a Job with region a en submit it on the nomad server in region b i get:

      * No nodes were eligible for evaluation
      * No nodes are available in datacenter "a1"

when i change the datacenter to b1 it works.
So it looks like the region is ignored.

Reproduction steps

  1. Setup 2 nomad servers and 2 nomad clients (A/B region setup)
  2. Create a job for region A
  3. Submit the job on region B

Job file (if appropriate)

job "example" {
    # Run the job in the global region, which is the default.
    region = "a"

    # Specify the datacenters within the region this job can run in.
    datacenters = ["a1"]
...
@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 Dec 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants