Rename a Cluster (Not a Node)

S

Shervin.Namakchian

New Member
Apr 22, 2025
3
1
3
Is it possible to rename a cluster?

It's been mentioned that this name cannot be changed later in the official document as follows:
https://pve.proxmox.com/wiki/Cluster_Manager

1745333188140.png

However, in another thread it's been mentioned that it's possible!
S

[SOLVED] Thread 'Rename a Cluster (Not a Node)'

Is it possible to rename a cluster?

I've only tried a few basic things, including stopping all relevant services and modifying /etc/corosync/corosync.conf (cluster_name: MyNewCluster), but it seems to be pulling the config from SQLite once I start everything back up?!

Ideally I wouldn't have to re-create everything!

Thanks!
  • Like

I'm not sure (confused) which one is correct, can you please share your experience with me.
 
Well my guess would be that it is technically possible but not recommended and not supported. I mean as the linked thread shows you need to be careful to not mess things up. So my question would be why you would do such a thing? You can always start a new cluster like this:

  • Migrate all vms and lxcs from the first node of the old cluster to the remaining nodes of it.
  • Reinstall PVE on the first node with new name for the cluster
  • Migrate the vms and lxcs from the second node of the old cluster to the first node of the new cluster and the remaining nodes of the old one
  • Reinstall PVE on the second node and join it to the new cluster
  • Rinse, repeat
With this procedure you should be able to move recreate a new cluster with the new name without actually having any downtime.
 
  • Like
Reactions: fba
Johannes S said:
Well my guess would be that it is technically possible but not recommended and not supported. I mean as the linked thread shows you need to be careful to not mess things up. So my question would be why you would do such a thing? You can always start a new cluster like this:

  • Migrate all vms and lxcs from the first node of the old cluster to the remaining nodes of it.
  • Reinstall PVE on the first node with new name for the cluster
  • Migrate the vms and lxcs from the second node of the old cluster to the first node of the new cluster and the remaining nodes of the old one
  • Reinstall PVE on the second node and join it to the new cluster
  • Rinse, repeat
With this procedure you should be able to move recreate a new cluster with the new name without actually having any downtime.
Click to expand...
Thank you Johannes for your time and suggestion, I'll consider that. However, we might not be able to do that due to some limitation.
 
We have come across the same situation as Shervin.Namakchian describes, though I'm not sure of Shervin's reason.

While purely cosmetic, the cluster name no longer represented either the brand, location or desired naming convention.

Renaming a Data Centre or cluster in vCenter is as easy as "right click, rename".

From what I have seen, renaming does work if done carefully, but is not supported. Rebuilding the entire cluster for a rename seems like overkill.
 
  • Like
Reactions: Shervin.Namakchian
I just renamed a Cluster we use for Testing, just for giggles and it worked.

I went into the Corosync file and changed the cluster_name.
/etc/pve/corosync.conf

Old-Name: pve-frg-tk
Bash: 
totem {
  cluster_name: pve-frg-tk
  config_version: 11
  interface {
    linknumber: 0
  }
  interface {
    linknumber: 1
  }
  ip_version: ipv4-6
  link_mode: passive
  secauth: on
  version: 2
}

New-Name: pve-frg-tk-new
Bash: 
totem {
  cluster_name: pve-frg-tk-new
  config_version: 12
  interface {
    linknumber: 0
  }
  interface {
    linknumber: 1
  }
  ip_version: ipv4-6
  link_mode: passive
  secauth: on
  version: 2
}

Attention: Every change you make you need to add +1 to the config_version!

After this I went into all nodes and restarted Corosync.
1745414323732.png

After Restarting Corosync and refreshing your page, you should see the new name.

I currently don't know if this has any side effects but atm. I don't experience any, everything works as normal.

So use at own risk!
 
Last edited:
  • Like
Reactions: LukasInCloud, Shervin.Namakchian and Octala_Alan
smueller said:
I just renamed a Cluster we use for Testing, just for giggles and it worked.

I went into the Corosync file and changed the cluster_name.
/etc/pve/corosync.conf

Old-Name: pve-frg-tk
Bash: 
totem {
  cluster_name: pve-frg-tk
  config_version: 11
  interface {
    linknumber: 0
  }
  interface {
    linknumber: 1
  }
  ip_version: ipv4-6
  link_mode: passive
  secauth: on
  version: 2
}

New-Name: pve-frg-tk-new
Bash: 
totem {
  cluster_name: pve-frg-tk-new
  config_version: 12
  interface {
    linknumber: 0
  }
  interface {
    linknumber: 1
  }
  ip_version: ipv4-6
  link_mode: passive
  secauth: on
  version: 2
}

Attention: Every change you make you need to add +1 to the config_version!

After this I went into all nodes and restarted Corosync.
View attachment 85284

After Restarting Corosync and refreshing your page, you should see the new name.

I currently don't know if this has any side effects but atm. I don't experience any, everything works as normal.

So use at own risk!
Click to expand...
Thank you @smueller for sharing your experience, appreciate that.
 
  • Like
Reactions: smueller
FYI:
We have tested it on our Test Custer for a wile, with HA and all basic features. We didn't experiences any issues.

But still be careful, it may still have a Issue that we didn't found!
 
You must log in or register to reply here.
Top Bottom