mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
6d17a9bf64
During allocation recovery, the go-plugin reattachment workflow checks to see if the PID we stored in client state is still running. If so, we try to connect to that process. If that fails, we kill the process under the presumption it's not working. But during reattachment we don't know that the PID we have is still valid. Which means that the process we're trying to attach to may have exited and a different process has spawned with the same PID. This results in some unrelated process getting silently killed. Update go-plugin to 1.6.2, which includes a bug fix so we do not kill the process. Fixes: https://github.com/hashicorp/nomad/issues/23969
4 lines
150 B
Plaintext
4 lines
150 B
Plaintext
```release-note:bug
|
|
deps: Fixed a bug where restarting Nomad could cause an unrelated process with the same PID as a failed executor to be killed
|
|
```
|