From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Kefu Chai <k.chai@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH ceph squid-stable-9 v3 0/1] patches: link the PVE cephx migration docs in the insecure key warnings
Date: Thu, 12 Nov 2026 11:56:38 +0100 [thread overview]
Message-ID: <s8ov762b9nd.fsf@toolbox> (raw)
In-Reply-To: <20261112082059.654926-1-k.chai@proxmox.com> (Kefu Chai's message of "Thu, 12 Nov 2026 16:20:58 +0800")
Kefu Chai <k.chai@proxmox.com> writes:
> The point releases added health checks for keys, service tickets and
> cipher settings that still use aes, and a PVE user picking up the
> release sees AUTH_INSECURE_KEYS_ALLOWED in `ceph health` with no hint
> what to do about it. Append the PVE cephx migration guide's URL to
> that check's summary, so the output itself points at the documented
> migration path.
>
> The sibling patch for tentacle-stable-9 is resent separately.
>
> Both patches were tested in a lab environment, on three-node clusters
> running packages built from these branches at 19.2.7-pve1 and
> 20.2.5-pve1: the URL shows up in `ceph health`, `ceph -s`, `ceph
> health detail` and the cluster log while the monitors still allow
> aes, and it disappears once the allowed ciphers are restricted to
> aes256k.
>
> Changes since v2:
>
> * rebase onto the Squid 19.2.7 import. The quilt patch itself is
> unchanged.
>
> Link to v2: https://lore.proxmox.com/pve-devel/20261016103138.3896717-1-k.chai@proxmox.com/
>
> Kefu Chai (1):
> patches: link the PVE cephx migration docs in the insecure key warnings
>
> patches/0058-mon-AuthMonitor-link-the-PVE-cephx-migration-docs-in.patch | 53 +++++++++++++++++++
> patches/series | 1 +
> 2 files changed, 54 insertions(+)
Tested creating a cluster with ceph 19.2.3-pve4 with a single VM using a
rbd storage. Upgraded the cluster to 19.2.7 with this patch applied and
carried the cephx key migration.
It all worked as expected. After restarting the first monitor after the
upgrade, ceph -s displayed as expected:
Monitors are configured to allow auth using insecure key types, see https://pve.proxmox.com/pve-docs/chapter-pveceph.html#pveceph_cephx_migration
Tested-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
Reviewed-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
--
Maximiliano
next prev parent reply other threads:[~2026-11-12 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 8:20 [PATCH ceph squid-stable-9 v3 0/1] patches: link the PVE cephx migration docs in the insecure key warnings Kefu Chai
2026-11-12 8:20 ` [PATCH ceph squid-stable-9 v3 1/1] " Kefu Chai
2026-11-12 10:56 ` Maximiliano Sandoval [this message]
2026-11-18 4:23 ` [PATCH ceph squid-stable-9 v3 0/1] " Kefu Chai
2026-11-18 14:51 ` applied: " Thomas Lamprecht
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=s8ov762b9nd.fsf@toolbox \
--to=m.sandoval@proxmox.com \
--cc=k.chai@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