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 57AF11FF0B3 for ; Wed, 28 Oct 2026 10:58:25 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id CE4792120A; Wed, 28 Oct 2026 10:58:24 +0100 (CET) From: Kefu Chai 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 Message-ID: <20261028095811.2408095-2-k.chai@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261028095811.2408095-1-k.chai@proxmox.com> References: <20261028095811.2408095-1-k.chai@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1793181495946 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.283 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: D7FHJO24LCE6SBVFSGA6SVMTIS5RE6S6 X-Message-ID-Hash: D7FHJO24LCE6SBVFSGA6SVMTIS5RE6S6 X-MailFrom: k.chai@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: 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 --- 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