Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

when nomad alloc stop invoked in allocation status doesn't show "Waiting %v before force killing" #5931

Closed
tantra35 opened this issue Jul 5, 2019 · 2 comments · Fixed by #5943

Comments

@tantra35
Copy link
Contributor

tantra35 commented Jul 5, 2019

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

@preetapan 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
@preetapan
Copy link
Contributor

@tantra35 Thanks for reporting, #5943 fixes it.

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants