all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Kefu Chai <k.chai@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH cluster/manager 0/2] fix #6501: allow cluster names up to 32 characters
Date: Wed, 28 Oct 2026 17:58:09 +0800	[thread overview]
Message-ID: <20261028095811.2408095-1-k.chai@proxmox.com> (raw)

The cluster name is limited to 15 characters. The limit dates back to
2011, when clusters ran on cman. corosync 3, corosync-qdevice and
pmxcfs handle longer names, so this series raises the limit to 32, in
the cluster create API (pve-cluster) and in the create dialog
(pve-manager). The allowed characters stay the same.

On master and on stable-bookworm (pve-cluster 8.1), the name is only
checked when a cluster is created. Joining a node copies corosync.conf
as is, and parse_conf, pmxcfs and qnetd don't limit the name. So older
nodes, including ones that join later, should work with a longer name,
and so should a downgrade. The reporter also says a longer name set in
corosync.conf by hand works for them.

On a single node, the two packages can be upgraded in either order:

- new pve-cluster, old pve-manager: the GUI still stops at 15, while
  pvecm and the API take 32
- old pve-cluster, new pve-manager: the GUI takes 32, but the API
  rejects anything over 15 ("value may only be 15 characters long")
  before creating anything

The second case is confusing but harmless. Bumping pve-manager's
dependency on libpve-cluster-api-perl, which ships the API, would avoid
it.

With a QDevice, the name is also the CN of the cluster's certificate,
which qnetd checks. RFC 5280 limits a CN to 64 characters, so 32 is
fine.

I tested this on a three-node lab cluster. The API accepts a
32-character name and rejects 33. After I renamed the cluster to a
32-character name in corosync.conf, it stayed quorate, and pmxcfs,
pvecm status and the cluster status and join info APIs showed the new
name. I couldn't test a join or mixed versions there, so that part is
from reading the code. Please let me know if I missed something.

pve-cluster:

Kefu Chai (1):
  fix #6501: api: cluster create: allow cluster names up to 32 characters

 src/PVE/API2/ClusterConfig.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

pve-manager:

Kefu Chai (1):
  fix #6501: ui: cluster create: allow cluster names up to 32 characters

 www/manager6/dc/ClusterEdit.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.47.3




             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 Kefu Chai [this message]
2026-10-28  9:58 ` [PATCH pve-cluster 1/2] fix #6501: api: cluster create: allow cluster names up to 32 characters Kefu Chai
2026-10-28  9:58 ` [PATCH manager 2/2] fix #6501: ui: " 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-1-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal