Skip to content

Conversation

vishaangelova
Copy link
Contributor

@vishaangelova vishaangelova commented Jul 30, 2025

This PR adds a known issue for Elastic Agents getting stuck in an upgrade scheduled state.

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)

@vishaangelova vishaangelova requested a review from a team as a code owner July 30, 2025 11:39
Copy link

github-actions bot commented Jul 30, 2025

🔍 Preview links for changed docs


:::{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**
Copy link
Member

Choose a reason for hiding this comment

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

8.18+8.19 as well

Copy link
Contributor Author

Choose a reason for hiding this comment

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

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I’ve added the rest of the versions here, too. Hopefully, this way there won't be any confusion.

@vishaangelova vishaangelova requested a review from cmacknz July 30, 2025 16:53
Copy link
Contributor

@karenzone karenzone left a comment

Choose a reason for hiding this comment

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

I asked a question wrt dates inline, seeking more info.
This comment is NOT BLOCKING, so LGTM.


**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

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

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.

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.

@vishaangelova vishaangelova merged commit b480f94 into main Jul 30, 2025
8 checks passed
@vishaangelova vishaangelova deleted the 2285-add-a-known-issue branch July 30, 2025 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Elastic Agent] Add a known issue for agents getting stuck in a scheduled state

4 participants