Skip to content

Add a known issue for Elastic Agents getting stuck in an upgrade scheduled state #2324

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.

Sign up for GitHub

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

Merged
merged 5 commits into from
Jul 30, 2025
Merged

Add a known issue for Elastic Agents getting stuck in an upgrade scheduled state #2324

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
65dc960
Add a known issue for agents getting stuck in a scheduled state
vishaangelova Jul 30, 2025
deb8c46
Apply suggestions from code review
vishaangelova Jul 30, 2025
665390b
Improve wording
vishaangelova Jul 30, 2025
3d76a82
Add issue also applies for versions 8.18.x and 8.19.0
vishaangelova Jul 30, 2025
5a36eaa
Merge branch 'main' into 2285-add-a-known-issue
vishaangelova Jul 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions release-notes/fleet-elastic-agent/known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,38 @@ Known issues are significant defects or limitations that may impact your impleme

% :::

:::{dropdown} {{agents}} remain in an "Upgrade scheduled" state

**Applies to: {{agent}} 8.18.0, 8.18.1, 8.18.2, 8.18.3, 8.18.4, 8.19.0, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.1.0**

On July 2, 2025, a known issue was discovered where {{agent}} remains in an `Upgrade scheduled` state when a scheduled {{agent}} upgrade is cancelled. Attempting to restart the upgrade on the UI returns an error: `The selected agent is not upgradeable: agent is already being upgraded.`.
Copy link
Contributor

@karenzone karenzone Jul 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't think I've ever seen a discovery date in a known issue. Is this something we're doing now? Does it help our users in anyway?

Copy link
Contributor Author

@vishaangelova vishaangelova Jul 30, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question… I was following the template at the beginning of the file to stay consistent with the rest of the known issues. But you’re right, I’m not sure if that’s of any help to users. I see some other known issue templates don’t have this, and some do.. Let’s talk about this with the team.

Copy link

@nicpenning nicpenning Jul 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it is of help to us users and it has been revealed in other known issues as well.

As a user, I like to see this sot hat I have an idea on how long it's been known this an issue as this gives some sort of idea on how long before a fix may come along. The longer an issue as been known about, generally the sooner an impending fix may be available.


For more information, check [Issue #8778](https://github.com/elastic/elastic-agent/issues/8778).

**Workaround**

Call the [Upgrade an agent](https://www.elastic.co/docs/api/doc/kibana/operation/operation-post-fleet-agents-agentid-upgrade) endpoint of the Kibana Fleet API with the `force` parameter set to `true` to force-upgrade the {{agent}}:

```powershell
curl --request POST \
--url https://<KIBANA_HOST>/api/fleet/agents/<AGENT_ID>/upgrade \
--user "<SUPERUSER_NAME>:<SUPERUSER_PASSWORD>" \
--header 'Content-Type: application/json' \
--header 'kbn-xsrf: true' \
--data '{"version": "<VERSION>","force": true}'
```

To force-upgrade multiple {{agents}}, call the [Bulk upgrade agents](https://www.elastic.co/docs/api/doc/kibana/operation/operation-post-fleet-agents-bulk-upgrade) endpoint of the Kibana Fleet API with the `force` parameter set to `true`:

```powershell
curl --request POST \
--url https://<KIBANA_HOST>/api/fleet/agents/bulk_upgrade \
--user "<SUPERUSER_NAME>:<SUPERUSER_PASSWORD>" \
--header 'Content-Type: application/json' \
--header 'kbn-xsrf: true' \
--data '{"version": "<VERSION>","force": true,"agents":["<AGENT_IDS>"]}'
```
:::

:::{dropdown} [Windows] {{agent}} is unable to re-enroll into {{fleet}}

Expand Down
Loading