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

[Fleet] Introduce new unexpected upgrade state for agents that upgraded unexpectedly #196426

Open
cmacknz opened this issue Oct 15, 2024 · 1 comment
Labels
QA:Needs Validation Issue needs to be validated by QA Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@cmacknz
Copy link
Member

cmacknz commented Oct 15, 2024

Describe the feature:

Converting the suggestion in elastic/fleet-server#3991 (comment) into a concrete feature addition. It is possible for agents to report that they are upgrading or that they have upgraded without receiving a corresponding action from Fleet. The most common way for this to occur today is to execute the elastic-agent upgrade command for a Fleet managed agent, but it could also occur as a result of a bug.

When an agent with no matching upgrade action ID reports upgrade details, the Fleet UI should flag the agent has upgrading unexpectedly to bring it to the operator's attention.

@cmacknz cmacknz added the Team:Fleet Team label for Observability Data Collection Fleet team label Oct 15, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA:Needs Validation Issue needs to be validated by QA Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

3 participants