-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Updating service in consul is not working #9763
Comments
Hi @SeaLife! I suspect this is another case of #9360 and #9735, which was fixed in #9736. I'm going to tag in my colleague @drewbailey who authored that PR to verify that. If so, the fix for this will ship in Nomad 1.0.2 |
Hey! Thanks for helping me out! :) Regards |
We don't have a Nomad 1.0.2 date set. We don't currently ship nightly builds (although I think it's been discussed) but with a golang 1.15 environment set up you can build via:
and get the same build we use in our nightly E2E testing. |
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. |
Hey guys,
my nomad cluster is not updating the service in consul correctly.
I found a similar issue here: #9358.
The problem is probably, that the labels for my ports are not found, but as far as i know, i created my nomad job file correctly:
Log output:
I've defined the port with the label "http" and im using this label in the service stanza, but still, its not working 🤔
Version Outputs:
Regards
SeaLife
The text was updated successfully, but these errors were encountered: