From 19df7b9eddc1701a53dca46c354e9303a743a92d Mon Sep 17 00:00:00 2001 From: Visha Angelova Date: Wed, 30 Jul 2025 15:29:55 +0200 Subject: [PATCH 1/3] Add a known issue for agents getting stuck in a scheduled state --- .../release-notes/release-notes-8.19.asciidoc | 43 +++++++++++++++++++ 1 file changed, 43 insertions(+) diff --git a/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc b/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc index 2866f20db..2b6f993b1 100644 --- a/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc +++ b/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc @@ -38,6 +38,49 @@ Review important information about the {fleet} and {agent} 8.19.0 release. {fleet-server}:: * Upgrade golang.org/x/net to v0.34.0 and golang.org/x/crypto to v0.32.0. {fleet-server-pull}4405[#4405] +[discrete] +[[known-issues-8.19.0]] +=== Known issues + +{agent}:: + +[[known-issue-issue#]] +.{agents} remain in an "Upgrade scheduled" state +[%collapsible] +==== + +*Details* + + +There is a known issue where after a scheduled {agent} upgrade is cancelled, {agent} remains in an `Upgrade scheduled` state, and attempting to restart the upgrade on the UI returns an error: `The selected agent is not upgradeable: agent is already being upgraded.`. + +*Impact* + + +Until this issue is fixed in a later patch version, you can call the https://www.elastic.co/docs/api/doc/kibana/operation/operation-post-fleet-agents-agentid-upgrade[Upgrade an agent] endpoint of the Kibana Fleet API with the `force` parameter set to `true` to force-upgrade the {agent}: + +[source,shell] +---- +curl --request POST \ + --url https:///api/fleet/agents//upgrade \ + --user ":" \ + --header 'Content-Type: application/json' \ + --header 'kbn-xsrf: as' \ + --data '{"version": "","force": true}' +---- + +To force-upgrade multiple {agents}, call the https://www.elastic.co/docs/api/doc/kibana/operation/operation-post-fleet-agents-bulk-upgrade[Bulk upgrade agents] endpoint of the Kibana Fleet API with the `force` parameter set to `true`: + +[source,shell] +---- +curl --request POST \ + --url https:///api/fleet/agents/bulk_upgrade \ + --user ":" \ + --header 'Content-Type: application/json' \ + --header 'kbn-xsrf: as' \ + --data '{"version": "","force": true,"agents":[""]}' +---- + +==== + [discrete] [[new-features-8.19.0]] === New features From 4d4813b77ec3e473e78bbcb58c7de2e4de30fbf8 Mon Sep 17 00:00:00 2001 From: Visha Angelova Date: Wed, 30 Jul 2025 17:04:49 +0200 Subject: [PATCH 2/3] Fix typo --- .../release-notes/release-notes-8.19.asciidoc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc b/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc index 2b6f993b1..f9876a303 100644 --- a/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc +++ b/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc @@ -42,9 +42,7 @@ Review important information about the {fleet} and {agent} 8.19.0 release. [[known-issues-8.19.0]] === Known issues -{agent}:: - -[[known-issue-issue#]] +[[known-issue-2285-8.19.0]] .{agents} remain in an "Upgrade scheduled" state [%collapsible] ==== From df22b99b190c1cf1ae1eebd6143690ae1b05b757 Mon Sep 17 00:00:00 2001 From: Visha Angelova Date: Wed, 30 Jul 2025 18:40:27 +0200 Subject: [PATCH 3/3] Improve wording --- .../release-notes/release-notes-8.19.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc b/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc index f9876a303..ae78a6602 100644 --- a/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc +++ b/docs/en/ingest-management/release-notes/release-notes-8.19.asciidoc @@ -49,7 +49,7 @@ Review important information about the {fleet} and {agent} 8.19.0 release. *Details* + -There is a known issue where after a scheduled {agent} upgrade is cancelled, {agent} remains in an `Upgrade scheduled` state, and attempting to restart the upgrade on the UI returns an error: `The selected agent is not upgradeable: agent is already being upgraded.`. +There is a known issue 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.`. *Impact* + @@ -61,7 +61,7 @@ curl --request POST \ --url https:///api/fleet/agents//upgrade \ --user ":" \ --header 'Content-Type: application/json' \ - --header 'kbn-xsrf: as' \ + --header 'kbn-xsrf: true' \ --data '{"version": "","force": true}' ---- @@ -73,7 +73,7 @@ curl --request POST \ --url https:///api/fleet/agents/bulk_upgrade \ --user ":" \ --header 'Content-Type: application/json' \ - --header 'kbn-xsrf: as' \ + --header 'kbn-xsrf: true' \ --data '{"version": "","force": true,"agents":[""]}' ----