[Fleet] Add upgrade_details.metadata.reason to AgentResponseSchema#252485
Merged
jillguyonnet merged 2 commits intoelastic:mainfrom Feb 10, 2026
Merged
[Fleet] Add upgrade_details.metadata.reason to AgentResponseSchema#252485jillguyonnet merged 2 commits intoelastic:mainfrom
jillguyonnet merged 2 commits intoelastic:mainfrom
Conversation
jillguyonnet
added
the
release_note:skip
jillguyonnet
added
Team:Fleet
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
elastic-vault-github-plugin-prod
Bot
requested a review
from a team
as a code owner
Contributor
⏳ Build in-progress, with failures
Failed CI Steps |
juliaElastic
approved these changes
Feb 10, 2026
Contributor
|
Starting backport for target branches: 9.3 https://github.com/elastic/kibana/actions/runs/21864828645 |
kibanamachine
added a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 10, 2026
…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)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Feb 10, 2026
…ema (#252485) (#252528) # Backport This will backport the following commits from `main` to `9.3`: - [[Fleet] Add upgrade_details.metadata.reason to AgentResponseSchema (#252485)](#252485) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jill Guyonnet","email":"jill.guyonnet@elastic.co"},"sourceCommit":{"committedDate":"2026-02-10T12:26:45Z","message":"[Fleet] Add upgrade_details.metadata.reason to AgentResponseSchema (#252485)\n\n## Summary\n\n`upgrade_details.metadata.reason` is missing from `AgentResponseSchema`,\nthis PR adds it.\n\nI noticed it while testing agent upgrade rollback in dev mode, where\nstrict body validation is enforced (this does not cause errors in\nproduction mode, but it's still missing from the OAS).\n\nTesting: roll back a recently upgraded Fleet-managed Elastic Agent.\nAfter rollback, it should be queryable in Fleet UI without error.\n\n<img width=\"1728\" height=\"722\" alt=\"Screenshot 2026-02-02 at 16 58 07\"\nsrc=\"https://github.com/user-attachments/assets/047ab6ad-5cdd-46f0-96fe-40001ba2904a\"\n/>\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"97bf115d46812f90971ff28af2f3c938075a7439","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:version","v9.3.0","v9.4.0"],"title":"[Fleet] Add upgrade_details.metadata.reason to AgentResponseSchema","number":252485,"url":"https://github.com/elastic/kibana/pull/252485","mergeCommit":{"message":"[Fleet] Add upgrade_details.metadata.reason to AgentResponseSchema (#252485)\n\n## Summary\n\n`upgrade_details.metadata.reason` is missing from `AgentResponseSchema`,\nthis PR adds it.\n\nI noticed it while testing agent upgrade rollback in dev mode, where\nstrict body validation is enforced (this does not cause errors in\nproduction mode, but it's still missing from the OAS).\n\nTesting: roll back a recently upgraded Fleet-managed Elastic Agent.\nAfter rollback, it should be queryable in Fleet UI without error.\n\n<img width=\"1728\" height=\"722\" alt=\"Screenshot 2026-02-02 at 16 58 07\"\nsrc=\"https://github.com/user-attachments/assets/047ab6ad-5cdd-46f0-96fe-40001ba2904a\"\n/>\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"97bf115d46812f90971ff28af2f3c938075a7439"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/252485","number":252485,"mergeCommit":{"message":"[Fleet] Add upgrade_details.metadata.reason to AgentResponseSchema (#252485)\n\n## Summary\n\n`upgrade_details.metadata.reason` is missing from `AgentResponseSchema`,\nthis PR adds it.\n\nI noticed it while testing agent upgrade rollback in dev mode, where\nstrict body validation is enforced (this does not cause errors in\nproduction mode, but it's still missing from the OAS).\n\nTesting: roll back a recently upgraded Fleet-managed Elastic Agent.\nAfter rollback, it should be queryable in Fleet UI without error.\n\n<img width=\"1728\" height=\"722\" alt=\"Screenshot 2026-02-02 at 16 58 07\"\nsrc=\"https://github.com/user-attachments/assets/047ab6ad-5cdd-46f0-96fe-40001ba2904a\"\n/>\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"97bf115d46812f90971ff28af2f3c938075a7439"}}]}] BACKPORT--> --------- Co-authored-by: Jill Guyonnet <jill.guyonnet@elastic.co>
mbondyra
added a commit
to mbondyra/kibana
that referenced
this pull request
Feb 10, 2026
* commit '7dcc1fe3c205d2de0c3ca3f65804f21de09013c3': (285 commits) Enrich kbn-check-saved-objects-cli README with CI and manual usage docs (elastic#252557) [Discover] Add feature flag to make ESQL the default query mode (elastic#252268) Add maskProps.headerZindexLocation above to inspect component flyout (elastic#252543) [Security Solution][Atack/Alerts] Flyout header: Assignees (elastic#252190) Upgrade EUI to v112.3.0 (elastic#252315) [Fleet] Make save_knowledge_base async in streaming state machine (elastic#252328) Upgrade @smithy/config-resolver 4.3.0 → 4.4.6 (elastic#252457) [Lens as API] Add colorMapping support for XY charts (ES|QL data layers) (elastic#252051) [WorkplaceAI] Add Google Drive data source and connector (elastic#250677) [Scout] Move GlobalSearch FTR tests to Scout (elastic#252201) [EDR Workflows] Fix osquery pack results display when agent clock is skewed (elastic#251417) [Observability Onboarding] Apply integrations limit after dedup in parseIntegrationsTSV (elastic#252486) [Entity Analytics] Update `host.ip` aggregation to remove painless script (elastic#252426) Address `@elastic/eui/require-table-caption` lint violations across `@elastic/obs-presentation-team` files (elastic#251050) Consolidate JSON stringify dependencies (elastic#251890) [index mgmt] Use esql instead of query dsl to get the index count (elastic#252422) Add Usage API Plugin (elastic#252434) Cases All Templates page (elastic#250372) [Agent Builder] Default value for optional params in ESQL tools (elastic#238472) [Fleet] Add upgrade_details.metadata.reason to AgentResponseSchema (elastic#252485) ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
upgrade_details.metadata.reasonis missing fromAgentResponseSchema, 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.
Checklist
release_note:*label is applied per the guidelinesbackport:*labels.