From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 365501FF13E for ; Fri, 06 Feb 2026 16:06:16 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4767B7CBE; Fri, 6 Feb 2026 16:06:50 +0100 (CET) From: Aaron Lauterer To: pve-devel@lists.proxmox.com, Hannes Duerr Subject: Re: [PATCH pve-docs v2 1/3] pvecm: restructure "remove a cluster node" section Date: Fri, 6 Feb 2026 16:06:46 +0100 Message-ID: <177039036785.1228684.12225526100663702025.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260204105324.61841-1-h.duerr@proxmox.com> References: <20260204105324.61841-1-h.duerr@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1770390327553 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.012 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: EGEUBQCLM5W2Z3M7H3WBCNRUDL7IBAF4 X-Message-ID-Hash: EGEUBQCLM5W2Z3M7H3WBCNRUDL7IBAF4 X-MailFrom: a.lauterer@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Wed, 04 Feb 2026 11:53:22 +0100, Hannes Duerr wrote: > The old section did not have a clear structure or sequence to follow. > For example, the final point, `pvecm delnode`, was not included in the > list of steps required to remove the cluster node. > The new structure consists of prerequisites, steps to remove the cluster > node and how to rejoin the existing node. The steps are explained using > an example. > > [...] Applied with some smaller fixups, thanks! [1/3] pvecm: restructure "remove a cluster node" section commit: 6f6227c50384089237ef95a891bd7b872942d68b [2/3] pvecm: mention node removal from ha rules in cleanup steps commit: 61b861c17943275c7b9636cad127cd3a7befb70d [3/3] partially-fix #4670: pvecm: mention authorized key removal in cleanup steps commit: 71e0dea99a505cb66ff87125ffbcf431391ffd04