Tim Gross

Hi @ejweber! That's definitely not great UX in retrospect. The API error code is an unfortunate byproduct of the way we translate from RPC calls to HTTP API. I'm not...

Hi @RosieBaish! I was able to more-or-less confirm the behavior you're seeing, and as it turns out the behavior on client restart is only a symptom of a different problem....

Hi @shakor0! You've hit upon why we set up the lock bot recently: posts on long-closed issues get missed. Unfortunately that post was many months ago, so I'm not sure...

Potentially related issues: https://github.com/hashicorp/nomad/issues/12768 https://github.com/hashicorp/nomad/issues/10727

Doing a bit of issue cleanup here. Since we last checked in on this issue, Nomad has shipped the [devices](https://www.nomadproject.io/docs/internals/plugins/devices), [task driver](https://www.nomadproject.io/docs/internals/plugins/task-drivers), and [storage](https://www.nomadproject.io/docs/internals/plugins/csi) plugin interfaces. I'm going to close...

Hi @stswidwinski! That might also be at the root of https://github.com/hashicorp/nomad-driver-podman/issues/192 Thanks for opening this!

Hi @bfqrst! Thanks for opening this issue. The keyring being referred to here is new in 1.4.x and supports the new [Workload Identity](https://developer.hashicorp.com/nomad/docs/concepts/workload-identity) feature. When a new server joins the...

The total lack of `keyring.replicator` logs here is very suspicious to me. There's a trace log at the start of replication (which we won't see here as it looks like...

From that goroutine dump I see a couple of important bits of information: * There is only _one_ goroutine anywhere in `encrypter.go`, which means we're not deadlocked on any of...

I've got a draft PR open with one fix I see we need, but I don't think that's at all the cause here: https://github.com/hashicorp/nomad/pull/14987. Investigation continues!