From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id AC66E1FF0AE for ; Tue, 15 Sep 2026 12:51:30 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 71CFA215CC; Tue, 15 Sep 2026 12:51:27 +0200 (CEST) From: Friedrich Weber 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 Message-ID: <20260915105113.97791-1-f.weber@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1789469468790 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.800 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: RS4OTBGTS3XICQLRJB32VBZL6SY2W3PG X-Message-ID-Hash: RS4OTBGTS3XICQLRJB32VBZL6SY2W3PG X-MailFrom: f.weber@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: 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 --- 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