From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id F092D1FF13E for ; Fri, 06 Feb 2026 16:04:33 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 01A8D7AD5; Fri, 6 Feb 2026 16:05:08 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Hannes Duerr Subject: applied: [PATCH pve-docs v2 1/3] pvecm: restructure "remove a cluster node" section Date: Fri, 6 Feb 2026 16:03:23 +0100 Message-ID: <177039020006.2811184.18048109045434248820.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: 1770390195617 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.020 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 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: 4EVDRGKCMOWVNTFA7EMV2XHIHKDJEYLI X-Message-ID-Hash: 4EVDRGKCMOWVNTFA7EMV2XHIHKDJEYLI X-MailFrom: t.lamprecht@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, thanks! FYI: I fixed a few smaller issues and restructured this further in some follow-up commits, would be great if you could check them out to ensure I did not overlook something or the like. [1/3] pvecm: restructure "remove a cluster node" section commit: 3f94515a0663caef23cef91d98f22255cf07056f [2/3] pvecm: mention node removal from ha rules in cleanup steps commit: bf5ec028ee71ecac814c0000e61f9cbbf4ccf0db [3/3] partially-fix #4670: pvecm: mention authorized key removal in cleanup steps commit: 090634ee26243f7f4ef6113fd261d32b801006b8