ha-manager.adoc: add missing service states

[pve-docs.git] / ha-manager.adoc

diff --git a/ha-manager.adoc b/ha-manager.adoc
index b8852f6550f5f602e2b08303359bd10757cfbf62..7f407f16a345e184df0a23bf4c1c179a67779510 100644 (file)
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -205,6 +205,10 @@ request_stop::
 Service should be stopped. The CRM waits for confirmation from the
 LRM.
 
+stopping::
+
+Pending stop request. But the CRM did not get the request so far.
+
 started::
 
 Service is active an LRM should start it ASAP if not already running.
@@ -212,6 +216,11 @@ If the Service fails and is detected to be not running the LRM
 restarts it
 (see xref:ha_manager_start_failure_policy[Start Failure Policy]).
 
+starting::
+
+Pending start request. But the CRM has not got any confirmation from the
+LRM that the service is running.
+
 fence::
 
 Wait for node fencing (service node is not inside quorate cluster
@@ -234,6 +243,14 @@ error::
 Service is disabled because of LRM errors. Needs manual intervention
 (see xref:ha_manager_error_recovery[Error Recovery]).
 
+queued::
+
+Service is newly added, and the CRM has not seen it so far.
+
+disabled::
+
+Service is stopped and marked as `disabled`
+
 
 Local Resource Manager
 ~~~~~~~~~~~~~~~~~~~~~~
@@ -614,9 +631,11 @@ Error Recovery
 If after all tries the service state could not be recovered it gets
 placed in an error state. In this state the service won't get touched
 by the HA stack anymore. The only way out is disabling a service:
+
 ----
 # ha-manager set vm:100 --state disabled
 ----
+
 This can also be done in the web interface.
 
 To recover from the error state you should do the following: