You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if we do nomad alloc stop the in stoped allocation status will be shown only "Sent interrupt" in one of events, but we expect that phrase must be more complex and must be looks like this "Sent interrupt. Waiting %v before force killing"
we think that this is happening because neither one in this fragments event doens't fill event struct
preetapan
changed the title
when nomad alloc stop invocked in allocation status doens't show "Waiting %v before force killing"
when nomad alloc stop invoked in allocation status doesn't show "Waiting %v before force killing"
Jul 9, 2019
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
0.9.3
if we do
nomad alloc stop
the in stoped allocation status will be shown only "Sent interrupt" in one of events, but we expect that phrase must be more complex and must be looks like this "Sent interrupt. Waiting %v before force killing"we think that this is happening because neither one in this fragments event doens't fill event struct
https://github.com/hashicorp/nomad/blob/master/client/allocrunner/alloc_runner.go#L502
https://github.com/hashicorp/nomad/blob/master/client/allocrunner/taskrunner/lifecycle.go#L71
The text was updated successfully, but these errors were encountered: