[8.17] (backport #9562) fix: scheduled upgrade details state

[mergify]

What does this PR do?

This PR fixes how Elastic Agent persists and reports upgrade details across check-ins, restarts, cancellations, and expired scheduled upgrade actions.

Specifically:

• (95ab857) Ensures the Coordinator is initialized with the correct upgrade details, either from the upgrade marker file or queued Fleet actions.
• (95ab857, cabe8c7) Extends the ActionDispatcher logic to:
  • Deduplicate upgrade actions from the received fleetgateway actions by keeping only the first encountered upgrade in input order.
  • Correctly track when upgrade details need to be updated (new upgrade actions, cancellations, expirations, etc.).
  • Correctly handle upgrade action cancellations.
  • Correctly handle expired scheduled upgrade actions and keep persisting them until explicitly canceled or replaced by a newer upgrade action.
  • Correctly handle retried upgrade actions.
  • Correctly update upgrade details when an upgrade action is scheduled for a retry.
  • Correctly update the upgrade details to nil when an upgrade action is dispatched without an error.
• (a16a9f3) Refactors and extends related dispatcher tests to include an actual action queue and cover new flows (queueing, canceling, expiring).
• (3e7324e) Adds new integration tests under testing/integration/ess/scheduled_upgrade_details_test.go to verify that scheduled upgrade details are:
  • Reported correctly when received.
  • Reported correctly when expired.
  • Preserved across Agent restarts.
  • Cleared on cancel.

All the new business logic is captured by 95ab857 (+234 -126 lines changed) and cabe8c7 (+174 -20 lines changed)

Why is it important?

Previously, scheduled upgrade details could be lost or incorrectly reported:

• They were not consistently preserved across Agent restarts.
• Cancel actions did not clear the reported upgrade details.
• Expired scheduled upgrade actions were treated as ephemeral and not persisted.

These inconsistencies caused confusion in Fleet UI and sometimes left users unable to perform upgrades.
With this fix, users now get a consistent and accurate view of upcoming, active, or failed upgrades across the entire Agent lifecycle.

Checklist

• I have read and understood the pull request guidelines of this project.
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

None expected. This change only improves correctness of reported upgrade details.
Users upgrading to this version will see more consistent and reliable upgrade state reporting in Fleet.

How to test this PR locally

1. Run the new integration tests
2. Or build the code of this PR

• Provision a 9.1.2 cloud stack
• AGENT_PACKAGE_VERSION=9.1.1 EXTERNAL=true SNAPSHOT=true PLATFORMS="linux/arm64" PACKAGES="tar.gz" mage package (ty @ycombinator for the proposal)
• Install and enroll the Agent to Fleet
• Schedule an upgrade → check it is reported.
• Restart the Agent → check details persist.
• Cancel the upgrade → check details clear.

Screen.Recording.2025-08-26.at.5.12.03.PM.mov

Also I tested the approach mentioned here to force update an agent and everything is reflected correctly to the upgrade details

Screen.Recording.2025-08-27.at.12.42.49.AM.mov

(PS: For the needs of the videos above I compiled this PR with pseudo prior version 9.1.1)

Related issues

• Closes Agents remains in UPG_SCHEDULED state when upgrade action is cancelled #8778
• Closes Elastic-agent loses UPG_SCHEDULED status when restarted #9434

  ---

  This is an automatic backport of pull request fix: scheduled upgrade details state #9562 done by Mergify.

[mergify]

Cherry-pick of ff80471 has failed:

On branch mergify/bp/8.17/pr-9562
Your branch is up to date with 'origin/8.17'.

You are currently cherry-picking commit ff8047180.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   changelog/fragments/1756218044-fix-upgrade-details-state.yaml
	modified:   internal/pkg/agent/application/dispatcher/dispatcher.go
	modified:   internal/pkg/agent/application/dispatcher/dispatcher_test.go
	modified:   internal/pkg/agent/application/managed_mode.go
	modified:   testing/fleetservertest/ackableactions.go
	modified:   testing/fleetservertest/checkin.go
	modified:   testing/fleetservertest/models.go
	new file:   testing/integration/ess/scheduled_upgrade_details_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   internal/pkg/agent/application/actions/handlers/handler_action_upgrade_test.go
	both modified:   internal/pkg/agent/application/application.go
	both modified:   internal/pkg/agent/application/application_test.go
	both modified:   internal/pkg/agent/application/coordinator/coordinator.go
	both modified:   internal/pkg/agent/application/coordinator/coordinator_test.go
	both modified:   internal/pkg/agent/cmd/run.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[elastic-sonarqube]

Quality Gate passed

Issues
8 New issues
2 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
81.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 96872c2

History

• 💔 Build #25965 failed e06d18d
• 💔 Build #25951 failed 0f86f9c

cc @pkoutsovasilis