-
Notifications
You must be signed in to change notification settings - Fork 154
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
Increase waiting time and timeout for removal of agent files #4310
Conversation
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
This pull request does not have a backport label. Could you fix it @pchila? 🙏
NOTE: |
|
I think we should backport this to 8.12 and 8.13. Added the labels. |
* increase waiting time and timeout for removal of agent files (cherry picked from commit 2eecafb)
* increase waiting time and timeout for removal of agent files (cherry picked from commit 2eecafb)
* increase waiting time and timeout for removal of agent files (cherry picked from commit 2eecafb)
What does this PR do?
This PR increases the timeout for removing files during
elastic-agent uninstall
and slows down retries to give time to the OS (especially windows) to release locks on the agent files.This comes after checking the results of #4304 where we verified that no lingering agent processes were present when we still had some
access denied
errors on executable filesWhy is it important?
This should prevent failures in our integration tests where we install/uninstall agent in quick succession.
It's also something that should make the uninstall process more reliable on a slower (especially windows) machine by giving more time to the OS to release files.
On a machine that already managed to deal with the quicker timeout (linux/darwin) there could be a negligible slowdown (most likely none) due to the slower interval between attempts.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works./changelog/fragments
using the changelog tool[ ] I have added an integration test or an E2E testAuthor's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs
Questions to ask yourself