Add a known issue for Elastic Agents getting stuck in an upgrade scheduled state
#2324
Conversation
🔍 Preview links for changed docs |
| @@ -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}} 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.1.0** | |||
There was a problem hiding this comment.
I’ve added a known issue to the release notes for these releases in PR elastic/ingest-docs#1841 & elastic/ingest-docs#1842, not sure yet if we should mention older versions in the 9.x docs, but I’ll check with the team.
There was a problem hiding this comment.
I’ve added the rest of the versions here, too. Hopefully, this way there won't be any confusion.
|
|
||
| **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.`. |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
This PR adds a known issue for Elastic Agents getting stuck in an
upgrade scheduledstate.Contributes to closing #2285
Related to elastic/ingest-docs#1841 (PR for the 8.19 release)
Related to elastic/ingest-docs#1842 (PR for the 8.18.x releases)