Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Allow upgrade action to signal retry #1887
Allow upgrade action to signal retry #1887
Changes from 8 commits
1bb5966
f0af07d
f29d495
f21a7e1
890362d
d521281
f34221a
7b0e161
63e4904
f386789
567c5d2
18204bc
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how will we handle stale agent (older versions without retry in ack)? is it expected for them not to retry?
i'd say yes, just want to double check with your intentions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FieldUpgradeStartedAt
andFieldUpgradedAt
is used in Fleet UI side to set statusUpgrading
i wonder if we should mark
FieldUpgradedAt
in case of failed retry as it was not upgraded so far.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, a pre v8.6 agent that reports an error will set
FieldUpgradeStatus
tofailed
. However I'm not sure if it is able to send that ack as I don't think it could actually ack a failure.If it sends a successful upgrade ack
FieldUpgradeStatus
will be set to nil andFieldUpgradedAt
is set to the current time (keeping the current behaviour)@juliaElastic should we be setting
FieldUpgradedAt
and clearingFieldUpgradeStartedAt
in failure cases, or should we keep these attributes to their original values?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently there is no
Failed
agent status. So the agent can either remain inUpdating
or move back toHealthy
status. The error should be captured in action results similar to other action failures.So I think the agent can move back to
Healthy
state if the upgrade failed (supposing nothing changed for the agent) - this means settingFieldUpgradeStartedAt
to nil and leavingFieldUpgradedAt
at the previous value.