From 729ed53755266ef5562f18f5ad8d8a8339e3279f Mon Sep 17 00:00:00 2001
From: Bernardo Dal Seno <bdalseno@google.com>
Date: Thu, 5 Jan 2012 15:05:29 +0100
Subject: [PATCH] Document "gnt-node add" behavior in case of failure
Signed-off-by: Bernardo Dal Seno <bdalseno@google.com>
Reviewed-by: Iustin Pop <iustin@google.com>
---
man/gnt-node.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/man/gnt-node.rst b/man/gnt-node.rst
index 15b663cd0..794fc0aa9 100644
--- a/man/gnt-node.rst
+++ b/man/gnt-node.rst
@@ -64,6 +64,13 @@ The ``vm_capable``, ``master_capable``, ``ndparams``, ``diskstate`` and
``hvstate`` options are described in **ganeti**(7), and are used to set
the properties of the new node.
+The command performs some operations that change the state of the master
+and the new node, like copying certificates and starting the node daemon
+on the new node, or updating ``/etc/hosts`` on the master node. If the
+command fails at a later stage, it doesn't undo such changes. This
+should not be a problem, as a successful run of ``gnt-node add`` will
+bring everything back in sync.
+
Example::
# gnt-node add node5.example.com
--
GitLab