-
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
Elastic-Agent fails to uninstall on Windows and is marked as unupgradable #3952
Comments
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
We have had this happen in our internal InfoSec deployment. I believe the root cause is a missing elastic-agent/internal/pkg/agent/cmd/uninstall.go Lines 54 to 57 in 677b79c
elastic-agent/internal/pkg/agent/application/info/state.go Lines 15 to 30 in 677b79c
|
I tried to reproduce it with a
The uninstall leaves one log file behind, but it works. |
Yeah that is a separate bug where the agent still has the file open as we try to delete it. Here's an explanation of the upgrade marker file: elastic-agent/internal/pkg/agent/cmd/run.go Lines 611 to 633 in 7e80290
My main question at this point is what job the .installed marker is doing and whether it is important enough that we should prevent uninstall and upgrade actions from completing if we aren't installed. |
Closing this one in favor of #4051 |
For confirmed bugs, please report:
Elastic-Agent was installed and correctly working on a Windows laptop, the laptop was offline for days and the Elastic Stack it was communicating with was deleted from Elastic Cloud.
Then when trying to uninstall the agent to install a new one it refused to be uninstalled, Windows service manager could not stop the service nor could the task manger kill the process.
Here are the logs from trying to install the new agent:
Trying to uninstall the Elastic-Agent from
C:\Program Files\Elastic\Agent
also did not work and reported the same error, something like:Rebooting the machine and uninstalling the Elastic-Agent from
C:\Program Files\Elastic\Agent
worked.The text was updated successfully, but these errors were encountered: