Tim Gross

@Elpaggio I was interested in tapping to any personal expertise you had on the subject but you've just posted a bunch of LLM-generated content which undermines the trust we'd need...

Hi @akamensky! Because you have reschedules disabled as well, submitting the exact same jobspec is intentionally a no-op. There should be a workaround here, which is to stop the job...

Hi @TheSpbra1n! This one is tricky! The log message you're seeing is about GC on the client node, where we clean up the allocation directory on the client. The `nomad...

Thanks for the jobspec @TheSpbra1n. That spec looks fine to me, which leads me back to wondering why the `Desired Status = run` still. The code that does job GC...

Thanks for that `job status` output @TheSpbra1n. That definitely looks suspiciously like the #10145 bug. I'm going to mark this issue for verifying once 1.0.5 ships. Thanks again!

Hi @TheSpbra1n! Have you had a chance to see if 1.0.5+ fixes the issue for you?

Doing some issue cleanup and I'm going to close this one out. If you do get a chance to test with Nomad 1.0.5+ or later and it doesn't fix the...

Hi @rahadiangg! I was able to reproduce this but it looks like it's intentional, although perhaps for an unfortunate reason. As far as the server is concerned, it's sending a...

Hi @ORuessel! If you take a look at the [Network Related Variables](https://developer.hashicorp.com/nomad/docs/reference/runtime-environment-settings#network-related-variables) docs you'll see the following comment underneath the table: > Nomad replaces characters that are neither alphanumeric nor...

See also https://github.com/hashicorp/nomad/issues/26989