[test] Fleet: the upgrade page does not explain how to roll back an Elastic Agent upgrade #9029

Activity

1. github-actions

   added

   needs-teamIssues pending triage by the Docs TeamIssues pending triage by the Docs Team

   on Oct 26, 2026
2. github-actions commented on Oct 26, 2026

   

   github-actionsBot

   on Oct 26, 2026 – with GitHub Actions

   Contributor

   More actions

   Elastic Docs AI Menu

   Check one box to run an AI workflow for this issue.

   • Scope the docs work (docs-scope). Status: not started.

   Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.
3. github-actions

   added

   Team:SKIIssues owned by the SKI Docs TeamIssues owned by the SKI Docs Team

   triagedTriage has been run on this issueTriage has been run on this issue

   and removed

   needs-teamIssues pending triage by the Docs TeamIssues pending triage by the Docs Team

   on Oct 26, 2026
4. theletterf commented on Oct 26, 2026

   

   theletterf

   on Oct 26, 2026

   MemberAuthor

   More actions

   /triage

   👀React with 👀1Reacted by github-actions
5. theletterf commented on Oct 26, 2026

   

   theletterf

   on Oct 26, 2026

   MemberAuthor

   More actions

   /scope

   👀React with 👀1Reacted by github-actions
6. github-actions commented on Oct 26, 2026

   

   github-actionsBot

   on Oct 26, 2026 – with GitHub Actions

   Last edited by github-actions

   Contributor

   More actions

   ✅ ScopeBot finished. https://github.com/elastic/docs-content/actions/runs/40307173790

   Generated from Gh Aw Issue Scope
7. github-actions commented on Oct 26, 2026

   

   github-actionsBot

   on Oct 26, 2026 – with GitHub Actions

   Last edited by github-actions

   Contributor

   More actions

   ✅ TriageBot finished. https://github.com/elastic/docs-content/actions/runs/40307170068

   Generated from Gh Aw Issue Triage
8. github-actions commented on Oct 26, 2026

   

   github-actionsBot

   on Oct 26, 2026 – with GitHub Actions

   Contributor

   More actions

   🟢 ScopeBot Results: Full assessment

   Summary

   The issue asks for a rollback section covering availability duration and configuration for Elastic Agent 9.2. The current Fleet upgrade page already documents the manual rollback path, states that rollback data is typically available for seven days, and says the feature requires both versions to be 9.3.0 or later; it does not document a configurable agent-upgrade rollback setting. The Kibana source also contains the Fleet agent rollback UI and an expired rollback-window error in the current default branch.

   Request accuracy

   Not verifiable against code. The published docs contradict the issue's 9.2 scope: manual Elastic Agent upgrade rollback is documented as available from 9.3.0+, while the separate integration rollback page documents a configurable xpack.fleet.integrationRollbackTTL setting.

   Recommended docs targets

   Page	URL	Action	Confidence	Why this page?
   Upgrade Fleet-managed Elastic Agents	https://www.elastic.co/docs/reference/fleet/upgrade-elastic-agent	Review only	High	The page already contains the relevant rollback section, including the Actions → Upgrade management → Roll back path, the seven-day availability window, cleanup behavior, and the 9.3.0+ applicability boundary.

   How to tackle this

   1. Confirm whether the request should target Elastic Agent 9.3.0+ rather than 9.2.
   2. If it targets agent-upgrade rollback, review the existing section for any remaining wording gap; do not add a configurable setting unless product source confirms one.
   3. If the requested setting is xpack.fleet.integrationRollbackTTL, update or link the existing Roll back an Elastic Agent integration page instead of the agent-upgrade page.
   4. If 9.2 behavior differs from the current documented behavior, provide the 9.2 product source or release-specific evidence before changing cumulative documentation.

   Scope boundary

   No new page or change to the standalone-agent upgrade procedure appears necessary; the integration rollback page should remain unchanged unless the request is actually about integration rollback TTL.

   Questions to go deeper

   • Is the intended product behavior Elastic Agent upgrade rollback in 9.3.0+, or integration rollback in 9.2?
   • Does Elastic Agent upgrade rollback have a configurable retention setting, or is the seven-day window fixed?
   • Is there 9.2-specific product or release evidence that conflicts with the current 9.3.0+ documentation boundary?

   This scope reflects the issue as of this run. Comment /scope to run it again after the issue changes.

   Generated from Gh Aw Issue Scope · ◷

   Scope requested by @theletterf. Was it helpful? When the work closes, add the label ai-scope:helpful or ai-scope:unhelpful to this issue.
9. theletterf commented on Oct 26, 2026

   

   theletterf

   on Oct 26, 2026

   MemberAuthor

   More actions

   Test finished. This was an automated test of the docs agentic workflows after the move to Agent Router (elastic/docs-eng-team#1056). Closing.
10. theletterf

    closed this as not plannedon Oct 26, 2026