Skip to content

[9.3] [Fleet] Add upgrade_details.metadata.reason to AgentResponseSchema (#252485)#252528

Merged
kibanamachine merged 3 commits intoelastic:9.3from
kibanamachine:backport/9.3/pr-252485
Feb 10, 2026
Merged

[9.3] [Fleet] Add upgrade_details.metadata.reason to AgentResponseSchema (#252485)#252528
kibanamachine merged 3 commits intoelastic:9.3from
kibanamachine:backport/9.3/pr-252485

Conversation

@kibanamachine
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.3:

Questions ?

Please refer to the Backport tool documentation

…lastic#252485)

## Summary

`upgrade_details.metadata.reason` is missing from `AgentResponseSchema`,
this PR adds it.

I noticed it while testing agent upgrade rollback in dev mode, where
strict body validation is enforced (this does not cause errors in
production mode, but it's still missing from the OAS).

Testing: roll back a recently upgraded Fleet-managed Elastic Agent.
After rollback, it should be queryable in Fleet UI without error.

<img width="1728" height="722" alt="Screenshot 2026-02-02 at 16 58 07"
src="https://github.com/user-attachments/assets/047ab6ad-5cdd-46f0-96fe-40001ba2904a"
/>

### Checklist

- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 97bf115)
@kibanamachine kibanamachine added the backport This PR is a backport of another PR label Feb 10, 2026
@kibanamachine kibanamachine enabled auto-merge (squash) February 10, 2026 12:35
@botelastic botelastic Bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Feb 10, 2026
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/fleet (Team:Fleet)

@kibanamachine kibanamachine merged commit 80a5d2a into elastic:9.3 Feb 10, 2026
13 checks passed
@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #71 / home app Welcome interstitial clicking on "Explore on my own" redirects to the "home" page
  • [job] [logs] Scout: [ observability / observability ] plugin / stateful - Observability Landing Page - redirects to Discover logs when logs data exists

Metrics [docs]

✅ unchanged

History

cc @jillguyonnet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR Team:Fleet Team label for Observability Data Collection Fleet team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants