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]: Create a known issue in fleet-server 8.12.0 and 8.12.1 #907

Closed
juliaElastic opened this issue Feb 9, 2024 · 0 comments · Fixed by #908
Closed

[REQUEST]: Create a known issue in fleet-server 8.12.0 and 8.12.1 #907

juliaElastic opened this issue Feb 9, 2024 · 0 comments · Fixed by #908
Assignees

Comments

@juliaElastic
Copy link
Contributor

juliaElastic commented Feb 9, 2024

Description

We found an issue with fleet-server 8.12.x: agents upgraded to 8.12.0 are stuck in non-upgradeable state, so the UI does not allow upgrade again to 8.12.1 and higher.

This is due do a bug introduced in 8.12.0 fleet-server where the agent last upgraded time (upgraded_at field) keeps incorrectly being updated on every checkin.

A fix is raised and planned for 8.12.2 and 8.13.0.

As a workaround, we suggest users to use the API to upgrade those agents with the force flag.
Example:

POST kbn:/api/fleet/agents/<agent_id>/upgrade
{
  "version": "8.12.1",
  "force": true
}

POST kbn:/api/fleet/agents/bulk_upgrade
  {
    "agents": "agent.version:8.12.0",
    "version": "8.12.1",
    "force": true
  }

Resources

elastic/fleet-server#3263

Collaboration

The documentation team will investigate the issue and create the initial content.

Point of contact.

Main contact: @juliaElastic

Stakeholders: @fleet

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