From: Kefu Chai <k.chai@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-cluster 1/2] fix #6501: api: cluster create: allow cluster names up to 32 characters
Date: Wed, 28 Oct 2026 17:58:10 +0800 [thread overview]
Message-ID: <20261028095811.2408095-2-k.chai@proxmox.com> (raw)
In-Reply-To: <20261028095811.2408095-1-k.chai@proxmox.com>
The 15 character limit was added in 2011, back when clusters ran on
cman. corosync 3, corosync-qdevice and pmxcfs have no such limit, and
the reporter says a longer name works for them after changing it in
corosync.conf by hand.
With a QDevice, the cluster name is also the CN of the cluster's TLS
certificate, which qnetd checks. RFC 5280 caps a CN at 64 characters.
Raise the limit to 32. That covers the requested 25 with room to spare.
Signed-off-by: Kefu Chai <k.chai@proxmox.com>
---
src/PVE/API2/ClusterConfig.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/API2/ClusterConfig.pm b/src/PVE/API2/ClusterConfig.pm
index bbed40e..c634ec9 100644
--- a/src/PVE/API2/ClusterConfig.pm
+++ b/src/PVE/API2/ClusterConfig.pm
@@ -102,7 +102,7 @@ __PACKAGE__->register_method({
description => "The name of the cluster.",
type => 'string',
format => 'pve-node',
- maxLength => 15,
+ maxLength => 32,
},
nodeid => get_standard_option('corosync-nodeid'),
votes => {
--
2.47.3
next prev parent reply other threads:[~2026-10-28 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 9:58 [PATCH cluster/manager 0/2] fix #6501: allow cluster names up to 32 characters Kefu Chai
2026-10-28 9:58 ` Kefu Chai [this message]
2026-10-28 9:58 ` [PATCH manager 2/2] fix #6501: ui: cluster create: " Kefu Chai
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=20261028095811.2408095-2-k.chai@proxmox.com \
--to=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