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] show upgrade retries #140225

Closed
michel-laterman opened this issue Sep 7, 2022 · 5 comments
Closed

[Fleet] show upgrade retries #140225

michel-laterman opened this issue Sep 7, 2022 · 5 comments
Labels
enhancement New value added to drive a business result Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@michel-laterman
Copy link

Part of the proposal for elastic/elastic-agent#778 would be to allow agents to retry certain actions (starting with the UPGRADE action).
In #139704 we suggest adding a new upgrade_status attribute to the agent documents in order to show when an agent is updating, or has completed its update.
When an agent is scheduled to retry an upgrade, the UI should reflect that state and show something like "retrying" instead of "updating", fleet-server will likely use the same upgrade_status attribute to show the upgrade state (instead of the top level agent status).

@michel-laterman michel-laterman added the Team:Fleet Team label for Observability Data Collection Fleet team label Sep 7, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@jen-huang jen-huang added the enhancement New value added to drive a business result label Sep 12, 2022
@nimarezainia
Copy link
Contributor

@michel-laterman @joshdover What would this signify to the user exactly? that we tried updating the agent but failed and now we are re-trying? i just want to make sure that we can prescribed what the user is to do if they see this status.

I agree that getting stuck in "Updating" state is not helpful and we need more context - but also want to find a way to help the operator to resolve.

@jlind23
Copy link
Contributor

jlind23 commented Oct 17, 2022

After discussing with @kpollich this will be moved to a later time.

@juliaElastic
Copy link
Contributor

@kpollich Should we close this in favor of https://github.com/elastic/ingest-dev/issues/1621 ?

@kpollich
Copy link
Member

Yep closing in favor of the private tracking issue

@kpollich kpollich closed this as not planned Won't fix, can't repro, duplicate, stale May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

7 participants