Add agent upgrade retry doc (#2230)

* Add agent upgrade retry doc * Fix retry aborting statement * Apply suggestions from code review Co-authored-by: DeDe Morton <[email protected]> Co-authored-by: DeDe Morton <[email protected]>
elastic · Oct 24, 2022 · c405cb7 · c405cb7
1 parent fbb6473
commit c405cb7
Showing 1 changed file with 6 additions and 1 deletion.
diff --git a/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc b/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc
@@ -14,6 +14,11 @@ maintenance window during which the upgrades will occur. If your {stack}
 subscription level supports it, you can schedule upgrades to occur at a specific
 date and time.
 
+In most failure cases the {agent} may retry an upgrade after a short wait. The
+wait durations between retries are: 1m, 5m, 10m, 15m, 30m, and 1h. During this
+time, the {agent} may show up as "retrying" in the {fleet} UI. Note that you
+can abort an upgrade that is being retried. See <<abort-agent-upgrade>>.
+
 This approach simplifies the process of keeping your agents up to date. It also
 saves you time because you don’t need third-party tools or processes to
 manage upgrades.
@@ -87,7 +92,7 @@ image::images/rolling-agent-upgrade.png[Menu for bulk upgrading {agent}s]
 
 . Select the amount of time available for the maintenance window. The upgrades
 are spread out uniformly across this maintenance window to avoid exhausting
-network resources. 
+network resources.
 +
 To force selected agents to upgrade immediately when the upgrade is
 triggered, select **Immediately**. Avoid using this setting for batches of more