From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <root@dev.dominic.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 8E4606520D for <pve-devel@lists.proxmox.com>; Wed, 22 Jul 2020 12:21:01 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 802641F780 for <pve-devel@lists.proxmox.com>; Wed, 22 Jul 2020 12:21:01 +0200 (CEST) Received: from dev.dominic.proxmox.com (212-186-127-178.static.upcbusiness.at [212.186.127.178]) by firstgate.proxmox.com (Proxmox) with ESMTP id DAE461F76D for <pve-devel@lists.proxmox.com>; Wed, 22 Jul 2020 12:21:00 +0200 (CEST) Received: by dev.dominic.proxmox.com (Postfix, from userid 0) id AF53C235A9; Wed, 22 Jul 2020 12:21:00 +0200 (CEST) From: =?UTF-8?q?Dominic=20J=C3=A4ger?= <d.jaeger@proxmox.com> To: pve-devel@lists.proxmox.com Date: Wed, 22 Jul 2020 12:20:52 +0200 Message-Id: <20200722102052.25546-2-d.jaeger@proxmox.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20200722102052.25546-1-d.jaeger@proxmox.com> References: <20200722102052.25546-1-d.jaeger@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 1 AWL 0.312 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods KHOP_HELO_FCRDNS 0.251 Relay HELO differs from its IP's reverse DNS NO_DNS_FOR_FROM 0.379 Envelope sender has no MX or A DNS records SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Subject: [pve-devel] [PATCH docs 2/2] pvecm: Add output for delnode X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Wed, 22 Jul 2020 10:21:01 -0000 The output of "pvecm delnode someNode" is "Killing node X". Even though this only says something about an attempt and not about success, it is not "no output is returned". Signed-off-by: Dominic Jäger <d.jaeger@proxmox.com> --- pvecm.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pvecm.adoc b/pvecm.adoc index 9207571..220c09f 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -327,11 +327,11 @@ After powering off the node hp4, we can safely remove it from the cluster. ---- hp1# pvecm delnode hp4 + Killing node 4 ---- -If the operation succeeds no output is returned, just check the node -list again with `pvecm nodes` or `pvecm status`. You should see -something like: +Use `pvecm nodes` or `pvecm status` to check the node list again. It should +look something like: ---- hp1# pvecm status -- 2.20.1