Commit 830fc5da authored by Andrea Spadaccini's avatar Andrea Spadaccini
Browse files

Document --ignore-errors and --error-codes

Update the man page of gnt-cluster to contain the documentation of the
--ignore-errors and --error-codes verify options. Also, include the list
of the error codes and their documentation.
Signed-off-by: default avatarAndrea Spadaccini <>
Reviewed-by: default avatarMichael Hanselmann <>
parent 3ac3f5e4
......@@ -619,7 +619,9 @@ node will be listed as /nodes/*name*, and an instance as
**verify** [--no-nplus1-mem] [--node-group *nodegroup*]
| **verify** [--no-nplus1-mem] [--node-group *nodegroup*]
| [--error-codes] [{-I|--ignore-errors} *errorcode*]
| [{-I|--ignore-errors} *errorcode*...]
Verify correctness of cluster configuration. This is safe with
respect to running instances, and incurs no downtime of the
......@@ -634,6 +636,39 @@ instances that live in the named group. This will not verify global
settings, but will allow to perform verification of a group while other
operations are ongoing in other groups.
The ``--error-codes`` option outputs each error in the following
parseable format: *ftype*:*ecode*:*edomain*:*name*:*msg*.
These fields have the following meaning:
Failure type. Can be *WARNING* or *ERROR*.
Error code of the failure. See below for a list of error codes.
Can be *cluster*, *node* or *instance*.
Contains the name of the item that is affected from the failure.
Contains a descriptive error message about the error
``gnt-cluster verify`` will have a non-zero exit code if at least one of
the failures that are found are of type *ERROR*.
The ``--ignore-errors`` option can be used to change this behaviour,
because it demotes the error represented by the error code received as a
parameter to a warning. The option must be repeated for each error that
should be ignored (e.g.: ``-I ENODEVERSION -I ENODEORPHANLV``). The
``--error-codes`` option can be used to determine the error code of a
given error.
List of error codes:
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment