From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Kefu Chai <k.chai@proxmox.com>
Cc: Jonas Theisen <j.theisen@proxmox.com>
Subject: applied: [PATCH manager v2 0/4] cephx: migrate keys with a monitor this cluster does not manage
Date: Mon, 19 Oct 2026 20:23:39 +0200 [thread overview]
Message-ID: <179243421710.2171626.5140844699955015642.b4-ty@b4> (raw)
In-Reply-To: <20261019082346.1781960-1-k.chai@proxmox.com>
On Mon, 19 Oct 2026 16:23:42 +0800, Kefu Chai wrote:
> A user reported an interesting stretch-cluster setup that
> pve-cephx-rotate-service-keys wasn't ready for: a tiebreaker monitor
> running on a standalone Proxmox VE host that isn't a node of the
> cluster itself, joined to the corosync quorum only through a QDevice
> and never listed under /etc/pve/nodes. All five monitors were in
> quorum and on the same, capable Ceph version, but the dry run still
> failed twice over:
>
> [...]
Applied, thanks!
[1/4] migrations: cephx: ask a monitor about itself through one route
https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=9b21b8d0e94cf4faa56ee3849180290e8999b00d
[2/4] migrations: cephx: judge cipher support by the version a daemon runs
https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=05d23944d932c5736a8a80e855ccda56f5f4d100
[3/4] migrations: cephx: rotate the monitor key with monitors we do not manage
https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=17b16f4f7a73636e03849d4005601be6f93b7bc5
[4/4] migrations: cephx: name the hosts keeping key copies we cannot write
https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=ef9dcc649cc86c14dd502bcd8c0313ba6333dc48
prev parent reply other threads:[~2026-10-19 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 8:23 [PATCH manager v2 0/4] cephx: migrate keys with a monitor this cluster does not manage Kefu Chai
2026-10-19 8:23 ` [PATCH manager v2 1/4] migrations: cephx: ask a monitor about itself through one route Kefu Chai
2026-10-19 8:23 ` [PATCH manager v2 2/4] migrations: cephx: judge cipher support by the version a daemon runs Kefu Chai
2026-10-19 8:23 ` [PATCH manager v2 3/4] migrations: cephx: rotate the monitor key with monitors we do not manage Kefu Chai
2026-10-19 8:23 ` [PATCH manager v2 4/4] migrations: cephx: name the hosts keeping key copies we cannot write Kefu Chai
2026-10-19 14:47 ` [PATCH manager v2 0/4] cephx: migrate keys with a monitor this cluster does not manage Jonas Theisen
2026-10-19 18:23 ` Thomas Lamprecht [this message]
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=179243421710.2171626.5140844699955015642.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=j.theisen@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