Status = failedDescription = Failed due to progress deadline
(1) What variable/parameter controls this message? "Task not running by deadline" in the worker allocation
(2) The worker actually started fine eventually... so it seems like the "Last Deployment" seems misleading... is there a way around this? We use this message to say that the deployment of the job is successful or not
hi guys, can we get the IP adderss of the allocations of the job using http api? i see the out of "nomad alloc status <allocid>" displaying the "Address" column. But the same is not available in REST response for EVAL. can anyone pls help here?
For a sample allocation of the example job: curl http://127.0.0.1:4646/v1/allocation/1ee54fa6-662d-f77e-3f41-253d9bce2f0d | jq '.AllocatedResources.Tasks.redis'
Will get you real close to it. There is a little more info you'd want to consume in there, like the port list, etc
But it's in the allocation api, not the evals one.
so I am running nomad node-drain -enable -self ... and sometimes it runs fast!
but sometimes it is so slow... as if it is waiting for something
and when I do ps aux | grep executor, I see that there are some nomad executors running which I assume the nomad drain is waiting for...
Probably. It also will wait to make sure that allocations have restarted when you are using the defaults.
like it depends on your parallelism
oh... I do have max_parallel = 3...
That can make it slow down.
While it waits for replacement allocations to start up
If I make the job version a consul value does that re-actively redeploy jobs if it changes?
Levant would trigger on that
levant would, but I'd need it running somewhere
I want to just push a change to consul and have prod carry out my intent
@the-maldridge how about a meta key used from inside Nomad's template syntax
then the Nomad agent would restart the job/task, right?
what just read the version and the meta tag from the same consul tag
I suppose that would work
but it does seem a bit clunky
@angrycub thanks that helped
Awesome! Glad that unblocked you.
@the-maldrige, maybe a consul watch?
on the version itself?
Is the version a k/v? If yes, a watch would do the trick for you
In my case I have a special salt module that handles a single k/v with a json object and I update only a specific value inside the json block
yes I'm wanting to have the version be a value at the end of the key
And a consul watch triggers a deploy using nomad under the hood whenever the k/v is updated and the job file hash changes
Since I run that in all my hashistack nodes I also use a consul lock to avoid multiple nodes pushing the same nomad job