-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Fleet] Prevent upgrades of agents already in updating state #133763
[Fleet] Prevent upgrades of agents already in updating state #133763
Conversation
Pinging @elastic/fleet (Team:Fleet) |
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.
Looks good to me 👍
@elasticmachine merge upstream |
1 similar comment
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: cc @criamico |
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit ba05c2c)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
Fixes #132992
Summary
Adding a check to the
isUpgradeable
function to make sure that an agent that is already inupdating
state doesn't get upgraded, both with regular and bulk upgrades. This function is used in many places so it means that anupdating
agent will deemed not upgradeable wherever we check it.Testing
updating
state, trigger the upgrade again, the endpoint should come back with an error similar toagent_id is not upgradeable
Checklist