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

No path to region #374

Closed
pschichtel opened this issue Jul 7, 2023 · 8 comments
Closed

No path to region #374

pschichtel opened this issue Jul 7, 2023 · 8 comments
Assignees

Comments

@pschichtel
Copy link

Hi, I've not actually found helpful information and I feel like it might actually be a bug in nomad-pack:

I have a rather simple pack for an internal application. It contains just one template. When I render it and deploy it with nomad job plan and nomad job run, then everything works fine as I'd expect it.

However, if I use nomad-pack plan or nomad-pack run directly, then I'm always presented with this output:

! Failed Job Conflict Validation

        Error:   No path to region
        Type:    *v1.APIError
        Context: 
                 - Template Name: kotlin_demo/templates/kotlin_demo.nomad.tpl

Nomad client version: v1.5.6 (from nomad version)
Nomad server version: 1.5.6 (from nomad server members)
Nomad-pack version: v0.0.1-techpreview.4 (50d84d0) (from nomad-pack version

@attachmentgenie
Copy link
Contributor

you seem to be hitting #266, good news is a fix will be released soon.

In the mean time you have to do export NOMAD_REGION=$YOURREGIONNAME nomad-pack run

@pschichtel
Copy link
Author

I looked at #266 and the related PR #366 and it seems this assumes I configured a region in my job spec, but I haven't. I guess my deployment relies on the server default, which nomad-pack doesn't use.

@pkazmierczak pkazmierczak self-assigned this Jul 10, 2023
@pschichtel
Copy link
Author

The documentation says "NOMAD_REGION - The region of the Nomad server to forward commands to. Defaults to the Agent's local region", I guess that default is simply missing?

@attachmentgenie
Copy link
Contributor

This is one of those times where nomad-pack currently is different from the vanilla nomad cli. Hence this confusing behaviour which has bitten me more than once. But as i said the nomad team has fixed this in #366, coming to a nightly/release near you soon

@pschichtel
Copy link
Author

Ah I just realized that your nightly tag isn't actually moved nightly. I'll build from master then.

@pschichtel
Copy link
Author

Yep, I can confirm it's working on main branch.

@pkazmierczak
Copy link
Contributor

Hey @pschichtel,

Ah I just realized that your nightly tag isn't actually moved nightly.

Apologies for this, I'll look into the CI config to see what's going on there. Happy to hear main build works as expected.

@pschichtel
Copy link
Author

I've setup two AUR package for nomad pack: nomad-pack-git (builds main) and nomad-pack-nightly (builds the nightly tag), so I'm covered for now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants