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

Backport of client: recover from getter panics into release/1.2.x #14705

Merged

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #14696 to be assessed for backporting due to the inclusion of the label backport/1.2.x.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

The below text is copied from the body of the original PR.


The artifact getter uses the go-getter library to fetch files from different sources. Any bug in this library that results in a panic can cause the entire Nomad client to crash due to a single file download attempt.

This change aims to guard against this types of crashes by recovering from panics when the getter attempts to download an artifact. The resulting panic is converted to an error that is stored as a task event for operator visibility and the panic stack trace is logged to the client's log.

@hashicorp-cla
Copy link

hashicorp-cla commented Sep 26, 2022

CLA assistant check
All committers have signed the CLA.

@lgfa29 lgfa29 force-pushed the backport/handle-getter-panic/radically-fancy-snail branch from 10ec2d6 to 724d2e7 Compare September 26, 2022 19:49
@lgfa29 lgfa29 requested a review from a team September 26, 2022 19:49
@lgfa29 lgfa29 requested a review from a team as a code owner September 26, 2022 19:49
@lgfa29 lgfa29 requested review from shore and modrake and removed request for a team September 26, 2022 19:49
The artifact getter uses the go-getter library to fetch files from
different sources. Any bug in this library that results in a panic can
cause the entire Nomad client to crash due to a single file download
attempt.

This change aims to guard against this types of crashes by recovering
from panics when the getter attempts to download an artifact. The
resulting panic is converted to an error that is stored as a task event
for operator visibility and the panic stack trace is logged to the
client's log.
@lgfa29 lgfa29 force-pushed the backport/handle-getter-panic/radically-fancy-snail branch from 724d2e7 to 6e407d4 Compare September 26, 2022 19:52
@lgfa29 lgfa29 removed request for a team, shore and modrake September 26, 2022 19:52
@lgfa29 lgfa29 merged commit bdb3409 into release/1.2.x Sep 26, 2022
@lgfa29 lgfa29 deleted the backport/handle-getter-panic/radically-fancy-snail branch September 26, 2022 20:09
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, 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 Jan 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants