From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Hannes Duerr <h.duerr@proxmox.com>
Subject: applied: [PATCH pve-docs v2 1/3] pvecm: restructure "remove a cluster node" section
Date: Fri, 6 Feb 2026 16:03:23 +0100 [thread overview]
Message-ID: <177039020006.2811184.18048109045434248820.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260204105324.61841-1-h.duerr@proxmox.com>
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
next prev parent reply other threads:[~2026-02-06 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 10:53 Hannes Duerr
2026-02-04 10:53 ` [PATCH pve-docs v2 2/3] pvecm: mention node removal from ha rules in cleanup steps Hannes Duerr
2026-02-04 10:53 ` [PATCH pve-docs v2 3/3] partially-fix #4670: pvecm: mention authorized key removal " Hannes Duerr
2026-02-06 8:33 ` [PATCH pve-docs v2 1/3] pvecm: restructure "remove a cluster node" section Maximiliano Sandoval
2026-02-06 15:03 ` Thomas Lamprecht [this message]
2026-02-06 15:06 ` Aaron Lauterer
2026-02-06 15:08 ` Aaron Lauterer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177039020006.2811184.18048109045434248820.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=h.duerr@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox