public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Friedrich Weber <f.weber@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs] cephx-migration: slightly rephrase and extend for clarity
Date: Tue, 15 Sep 2026 12:49:19 +0200	[thread overview]
Message-ID: <20260915105113.97791-1-f.weber@proxmox.com> (raw)

Namely:

- In the "Before You Begin" section, move the rolling restart to its
  own list item.

- When refreshing CephFS mounts, add a note that VMs with ISOs from
  a CephFS mount may need to be migrated (thanks Manuel!)

- In the finishing step, do not directly state the expected command
  to reduce the risk of users just copy-pasting the command (thanks
  Jonas!)

Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
---
 pveceph.adoc | 16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)

diff --git a/pveceph.adoc b/pveceph.adoc
index d0549ab..c46226e 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -1365,8 +1365,8 @@ without options to check the current state and follow the next steps it prints.
 .Before You Begin
 * Upgrade `pve-manager` to 9.2.17 or newer and install the latest Ceph
   packages on every node. Staged client-key rotation requires Ceph
-  19.2.6-pve3, 20.2.4-pve3, or newer on every monitor. Then complete the
-  rolling restart of all Ceph services.
+  19.2.6-pve3, 20.2.4-pve3, or newer on every monitor.
+* Then complete the rolling restart of all Ceph services.
 * Resolve health warnings and errors not listed in
   xref:pveceph_cephx_health_check_reference[Health Check Reference]. Ensure
   every node is reachable over SSH.
@@ -1464,6 +1464,9 @@ until confirmation makes the new key current and invalidates the old one.
 * The helper refreshes idle CephFS mounts and leaves busy or unresponsive
   mounts alone. Once nothing uses them, rerun the helper with `--apply` to
   retry the outstanding mounts.
+  If your virtual machines have ISOs from a CephFS mount attached, you may have
+  to detach the ISOs or migrate affected virtual machines to a different node
+  to be able to refresh the CephFS mount on that node.
 * For clients outside {pve}, distribute the staged credential from the
   xref:pveceph_cephx_external_copies[managed key files], then restart or remount
   those clients.
@@ -1491,13 +1494,8 @@ fail. Do not use `--force` to bypass a blocker.
 
 After checking disconnected clients and external copies, run the exact
 command the dry run prints. When every rotation is ready and no key needs the
-old cipher, it is:
-
-[source,bash]
-----
-/usr/share/pve-manager/migrations/pve-cephx-rotate-service-keys --apply \
-    --confirm-all-clients-refreshed --restrict-ciphers
-----
+old cipher, it will print the options `--apply --confirm-all-clients-refreshed
+--restrict-ciphers`.
 
 If any client remains incompatible, keep its key unchanged and the old cipher
 enabled rather than restricting it. You can
-- 
2.47.3





             reply	other threads:[~2026-09-15 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 10:49 Friedrich Weber [this message]
2026-09-15 13:17 ` applied: [PATCH docs] cephx-migration: slightly rephrase and extend for clarity Fabian Grünbichler

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=20260915105113.97791-1-f.weber@proxmox.com \
    --to=f.weber@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal