-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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]: Unable to upgrade agents on latest 8.4 Snapshot and fleet fails to detect correct version of installed agent during upgrade. #139006
Comments
@manishgupta-qasource Please review. |
Secondary review for this ticket is Done |
@amolnater-qasource do you know if the agent got the update command and rejected it or if the UI itself is preventing the upgrade? |
Hi @AndersonQ Further we have also observed that this issue still reproducible on latest 8.4 Snapshot. Build details: Please let us know if anything else is required from our end. Thanks |
Thanks @amolnater-qasource this error message seems to be a Kibana one. Maybe @kpollich and @elastic/fleet may be able to help here. |
We found the problem in kibana logic, the code doesn’t compare versions correctly, should be comparing the coerced versions: |
Hi @juliaElastic Observations:
Build details: Screen Recording: Agents.-.Fleet.-.Elastic.-.Google.Chrome.2022-08-22.10-20-09.mp4Hence marking this as QA:Validated. Thanks |
|
Kibana version: 8.4.0 Snapshot Kibana cloud environment
Host OS: All
Build details:
VERSION: 8.4.0
BUILD: 55248
COMMIT: 62ed40b
Artifact Link: https://artifacts.elastic.co/downloads/beats/elastic-agent/elastic-agent-8.3.0-linux-x86_64.tar.gz
Preconditions:
Integrations:
System
Steps to reproduce:
Upgrade Agent
for lower version agent.cannot upgrade agent to 8.4.0 because it is higher than the installed kibana version 8.4.0
for lower version agent.Screen Recording:
Agents.-.Fleet.-.Elastic.-.Google.Chrome.2022-08-10.19-57-40.mp4
Expected Result:
User should be able to upgrade agents to latest version on 8.4 Snapshot.
The text was updated successfully, but these errors were encountered: