-
Notifications
You must be signed in to change notification settings - Fork 148
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
[Agent Upgrade]: Agent upgrade fails on upgrade from 8.2.0>8.3.0-Snapshot and goes Unhealthy on all OS's. #526
Comments
Secondary review for this ticket is Done |
@samratbhadra-qasource are there any logs available on these unhealthy agents? |
Hi @joshdover
Please do let us know if anything else is required from our end. |
Not sure if this is related to a problem I am having. I'm running 8.2.2 with agents at 8.1.2 and when I attempt to upgrade them they go unhealthy. I did a procmon and found that after they download the zip file they look for c:\program files\elastic\agent\data\elastic-agent-[version code]\downloads\elastic-agent-8.2.2-windows-x86_64.zip.asc. I found that if I manually download and place that .asc file in the directory on a client then I can remotely upgrade them ok from fleet. |
@wearmg You're running into a known issue with agent upgrades on 8.1.2: https://www.elastic.co/guide/en/fleet/8.1/release-notes-8.1.2.html This feature is currently in beta, so we apologize for the bug here. You'll need to manually reinstall the agent on affected hosts (or use the workaround you discovered). |
This does appear to be a similar issue to #275, here are the logs from the diags provided above:
View JSON logs
@michel-laterman could you take a look? |
I'll try to recreate and investigate |
Thanks Josh, I have ~2,300 agents sitting like this. Just wrote a powershell script to drop the .asc file on them all and so far they are looking good and i'll just have to handle the handful of macs manually. |
I'm unable to recreate the same issue on an Ubuntu 20.04 VM. On the vm, the
There are no other agents or beats running on the instance. |
@michel-laterman I'll dig into this, this might be related to new upgrade changes that suppose to migrate all the agent configurations into encrypted format. |
Hi @aleksmaus
We have shared detailed observation at #173 Build details: Thanks! |
Description:
Agent upgrade fails on upgrade from 8.2.0>8.3.0-Snapshot and goes Unhealthy on all OS's.
Build Details:
VERSION: 8.3.0-Snapshot
BUILD: 53295
COMMIT: 6ef457053adce432a3b4d5b016997f92488d857d
ARTIFACT LINK OF 8.2.0 : https://www.elastic.co/downloads/past-releases/elastic-agent-8-2-0
Preconditions:
Steps to Reproduce:
Actual Result:
Agent upgrade fails on upgrade from 8.2.0>8.3.0-Snapshot and goes Unhealthy on all OS's.
Also, If agent is upgraded from 8.2.0>8.2.1 the agent gets upgraded to v8.2.1.
Further, if agent is upgraded from 8.2.1>8.3.0-Snapshot the agent fails to upgrade and rolls back to v8.2.0 and goes to unhealthy state.
Expected Result:
Agent upgrade should not fail on upgrade from 8.2.0>8.3.0-Snapshot and should not go to unhealthy state.
Screenshot:
Logs:
logs.zip
The text was updated successfully, but these errors were encountered: