-
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
Changes to connect stanza get ignored on job re-run #6459
Comments
This was referenced Dec 19, 2019
shoenig
added a commit
that referenced
this issue
Mar 20, 2020
shoenig
added a commit
that referenced
this issue
Mar 30, 2020
josemaia
added a commit
to josemaia/nomad
that referenced
this issue
Oct 20, 2020
Issue hashicorp#6459 has been fixed for a while, but the docs still point to it as a limitation
fredrikhgrelland
pushed a commit
to fredrikhgrelland/nomad
that referenced
this issue
Oct 22, 2020
Issue hashicorp#6459 has been fixed for a while, but the docs still point to it as a limitation
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If for example I have a
job.nomad
file with a consul connect stanza defined like,and then modify something like the
local_bind_port
to be something different,and then re-run the
job.nomad
job,I'd expect to see the change get applied, but nothing happens (the container is left as-is), e.g.
On the other hand, issuing a
job stop
andjob run
destroys everything and creates the new job with the changes as expected.From the logs, it seems the change gets ignored
The text was updated successfully, but these errors were encountered: