From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 E4AAF69D6E for ; Wed, 15 Sep 2021 15:36:59 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DBE8D1976C for ; Wed, 15 Sep 2021 15:36:29 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS id B022C19742 for ; Wed, 15 Sep 2021 15:36:28 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 84C96448B4 for ; Wed, 15 Sep 2021 15:36:28 +0200 (CEST) From: Dylan Whyte To: pve-devel@lists.proxmox.com Date: Wed, 15 Sep 2021 15:36:17 +0200 Message-Id: <20210915133618.143859-5-d.whyte@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20210915133618.143859-1-d.whyte@proxmox.com> References: <20210915133618.143859-1-d.whyte@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.464 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH pve-docs 5/6] pvecm: add note about corosync killnode error X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Sep 2021 13:36:59 -0000 Mentions the misleading error message shown, when deleting a node, because of the failing command: corosync-cfgtool -k x Some forum users were confused by this, and believed that the removal of the node was unsuccessful. Signed-off-by: Dylan Whyte --- pvecm.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/pvecm.adoc b/pvecm.adoc index af9cf33..e7140a6 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -340,6 +340,11 @@ After powering off the node hp4, we can safely remove it from the cluster. Killing node 4 ---- +NOTE: At this point, it is possible that you will receive an error message +stating `Could not kill node (error = CS_ERR_NOT_EXIST)`. This does not +signify an actual failure in the deletion of the node, but rather a failure in +corosync trying to kill an offline node. Thus, it can be safely ignored. + Use `pvecm nodes` or `pvecm status` to check the node list again. It should look something like: -- 2.30.2