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

[REQUEST]: Document "restart upgrade" cooldown for agents #605

Closed
kpollich opened this issue Oct 17, 2023 · 4 comments · Fixed by #609
Closed

[REQUEST]: Document "restart upgrade" cooldown for agents #605

kpollich opened this issue Oct 17, 2023 · 4 comments · Fixed by #609
Assignees

Comments

@kpollich
Copy link
Member

Description

We want to add a section to the docs somewhere that explains that there's a 10 minute cooldown between forcing a restart of an upgrade for agent to avoid overwhelming the agent.

Resources

elastic/kibana#168606

Collaboration

The product team will provide the initial content.

Point of contact.

Main contact: @kpollich

Stakeholders: @elastic/fleet

@kpollich
Copy link
Member Author

Thinking maybe we can add a block of text in or around this section: https://www.elastic.co/guide/en/fleet/current/upgrade-elastic-agent.html#upgrade-an-agent or here: https://www.elastic.co/guide/en/fleet/current/fleet-troubleshooting.html#fleet-agent-stuck-on-updating

If an agent's upgrade appears stuck, you may restart the upgrade process from the Fleet UI. Please note, however, that there is a 10 minute cooldown in between restart attempts.

@kpollich
Copy link
Member Author

We link to the "upgrade an agent" docs elsewhere in the "restart upgrade" modal so that's probably the right place.

@kilfoyle
Copy link
Contributor

Thanks for opening this @kpollich! I agree that the first page you linked to is the right spot. Here's a PR with that change (note that I had earlier updated the v8.11 and higher docs with the new "restart upgrade" function, so this looks a bit different from your link above).

By the way, I didn't realize we have a Troubleshooting section about stalled upgrades. I am thinking that with the new, more granular upgrade details shown on the UI and the new restart upgrade option that Julia added, that troubleshooting section may cause some confusion. I think maybe I should remove it from the 8.12 and later docs. What do you think?

@kpollich
Copy link
Member Author

+1 on removing those troubleshooting docs and directing users to the restart upgrades docs. Thanks this looks great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants