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

cli: fix panic on job restart #17346

Merged
merged 2 commits into from
May 30, 2023
Merged

cli: fix panic on job restart #17346

merged 2 commits into from
May 30, 2023

Conversation

lgfa29
Copy link
Contributor

@lgfa29 lgfa29 commented May 29, 2023

When monitoring the replacement allocation, if the Allocations().Info() request fails, the alloc variable is nil, so it should not be read.

Only backport to 1.5.x because that's when the nomad job restart was added.

Fixes #17329

When monitoring the replacement allocation, if the
`Allocations().Info()` request fails, the `alloc` variable is `nil`, so
it should not be read.
@lgfa29 lgfa29 requested review from angrycub and pkazmierczak May 29, 2023 17:33
Copy link
Contributor

@pkazmierczak pkazmierczak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@lgfa29 lgfa29 merged commit 389dff4 into main May 30, 2023
@lgfa29 lgfa29 deleted the b-fix-panic-on-job-restart branch May 30, 2023 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/1.5.x backport to 1.5.x release line
Projects
None yet
Development

Successfully merging this pull request may close these issues.

graceful restart of non-leader server agent makes active job evaluation segfault
2 participants