-
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
only one task group updates with rolling deploy #3000
Comments
Noticing now that these tasks are never marked as healthy when inspected from the nomad client, however, these service checks are passing in Consul. |
Hey only one would be deployed because of Do you have any interpolations in your check? That might mean you are getting hit by this: #2984 If not, you can change your clients log level to TRACE and information about why it hasn't transitioned to healthy will be printed. Nomad v0.6.1 will emit events to make debugging this easier. |
No interpolation in the status check. Simply an unauthenticated test against a health endpoint of an HTTP service. Transitioning to TRACE log level didn't produce much meaningful, mostly periodic Consul KV lookups. Any guidance on what I should be looking for? |
Yeah, Grep for |
Resolved. We missed a provisioning process, so our clients were still on v0.5.6 and I don't think the logging came in until v0.6.0. Since this appears to be a break between 0.5/0.6 compatibility, it'd be great if the 0.6 server emitted warn logs when the scenario exists. Thanks for the guidance on working through this. |
Glad you figured it out @goedelsoup |
I'm running into the same, server and two clients, all on 0.6.0. But if I understand correctly I'm hitting #2984 right? check {
type = "script"
# Direct curl somehow doesn't work?
command = "/bin/bash"
args = ["-c", "curl -sf -H 'Host: mysite.nl' ${NOMAD_ADDR_http}/status/"]
interval = "10s"
timeout = "2s"
} When are patches usually released? |
@tino 0.6.1 will be coming out within 2 weeks. I will push a binary to that issue that resolves this for those who are hitting it. |
Thanks. What do you mean by "push a binary to that issue"? |
Hey Tina,
I just meant I will upload binaries that have the fix: #2969 (comment)
- Alex Dadgar
…On Aug 10, 2017, 1:26 PM -0700, Tino de Bruijn ***@***.***>, wrote:
Thanks. What do you mean by "push a binary to that issue"?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
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. |
Nomad version
Nomad v0.6.0
Operating system and Environment details
Ubuntu 16.04
Issue
The following job only updates one task of the three deployed:
Since this is our staging environment, we are updating the snapshot build and forcing the image pull via
force_pull
. We attempted to force modify the job definition by injecting the Git commit SHA into a meta field.The job status shows the following (with only one job version bumped unless we first stop the job:
The text was updated successfully, but these errors were encountered: