Proxmox node name change
- Thread starter petka
- Start date
https://pve.proxmox.com/wiki/Renaming_a_PVE_node its a trap, warning.
It doesnt work
I still want to know how can I rename the hostname
It doesnt work
I still want to know how can I rename the hostname
I tried the method described below, but I can't copy the config files. It always says the file already exists, even though
ls doesn't show them.Also it turned out to replicate the qemu-server folder inside itself. Still haven't been able to change the name...
There should be an easy way to do this in the GUI. Also, that wiki page NEEDS to be updated. @tom @dietmar why respond to your users with incomplete steps and act like it's an easy thing to do when it's not?
Thank you @breakaway9000! This worked for me.
Thank you @breakaway9000! This worked for me.
Last edited:
this works except the storage disks in the left panel under storage is all gone....how can we also move the storage or make it display in the left panel?
I can concur that the wiki post is hot garbage and you will ruin your Proxmox host if you try this. Good thing I tried this in a lab first. Encountering the same issue where the nodes folder contents refused to copy. Gave it another reboot, and not sure what has happened, but now the entire nodes folder is empty, and my proxmox install is toast, won't even load the WebUI. Wonderful.
Last edited:
Hello,
Here we have a two-nodes cluster in which the hostnames of the nodes are OK, but their domain names are to be changed.
In all the setup changes your are all talking about, I see nowhere any mention of the domain name.
Would that imply that I can simply modify /etc/hosts and change the FQDN from node1.olddomain.com to node1.newdomain.com and just easily reboot?
Thank you
Here we have a two-nodes cluster in which the hostnames of the nodes are OK, but their domain names are to be changed.
In all the setup changes your are all talking about, I see nowhere any mention of the domain name.
Would that imply that I can simply modify /etc/hosts and change the FQDN from node1.olddomain.com to node1.newdomain.com and just easily reboot?
Thank you
The Wikipage https://pve.proxmox.com/wiki/Renaming_a_PVE_node is outdatet/not complete. I renamed a PVE 7 (standalone) instance and after the reboot no VM/CT came up.
Failure:
So it looks like the folder
Edit: found this link: https://erik.ellsinger.me/how-to-change-the-hostname-of-a-proxmox-node/ but does not work too.
Failure:
Configuration file 'nodes/$NEWHOSTNAME/lxc/100.conf' does not exist and so on.So it looks like the folder
/etc/pve/nodes/$OLDHOSTNAME needs to renamed/moved to /etc/pve/nodes/$NEWHOSTNAME too. But seems be not possible at runtime.Edit: found this link: https://erik.ellsinger.me/how-to-change-the-hostname-of-a-proxmox-node/ but does not work too.
Last edited:
Yep this is one of the things that I was hoping Proxmox 7 would resolve. Alas, it appears to be an ongoing issue
The only way that I've had success is to backup all my VMs, reinstall Proxmox, and restore all my VMs again. It's kind of a pain to do though.
The only way that I've had success is to backup all my VMs, reinstall Proxmox, and restore all my VMs again. It's kind of a pain to do though.
Try to
systemctl stop pveproxy.service the daemon and perform the rename with that stopped so it doesn't read the configurations while you're doing so (or try to stop you). Then it's systemctl start pveproxy.service to get it running again...Yes, I have done it on v7.2.3. First, I struggled like many of you, too. I finally succeeded by combining 2 major steps:
A)
As mentioned in https://pve.proxmox.com/wiki/Renaming_a_PVE_node I corrected the hostname to the new name in the following files:
- /etc/hosts
- /etc/hostname
- /etc/postfix/main.cf
B)
I followed the combined steps indicated by ikke and bryanpedini further up in this thread:
systemctl stop pveproxy.service- I emptied the folder
/etc/pve/nodes/$NEWHOSTNAME - I moved the contents of the folder
/etc/pve/nodes/$OLDHOSTNAMEto/etc/pve/nodes/$NEWHOSTNAME - I removed the folder
/etc/pve/nodes/$OLDHOSTNAME systemctl start pveproxy.service
TASK ERROR: storage 'YOUR-STORAGE-NAME' is not available on node 'OLDHOSTNAME'
Last edited:
When you follow the guide to rename your PVE node, but your node is not empty, you'll run into trouble like this (as noted before):
Or in case of trying to move the directory:
It seems this is due to the fact that the system detects that you're trying to create VMs with the same IDs.
I had success doing the following:
Slightly involved, but does the trick. Also, I'm not sure if it's necessary to stop the pve-cluster service, manually mount the fuse fs and then reboot.
I did it anyway for reasons of caution.
Code:
# cd /etc/pve/nodes
# cp -R old new
cp: cannot create regular file 'new/qemu-server/100.conf': File existsOr in case of trying to move the directory:
Code:
# mv old new
mv: cannot move 'old' to 'new': Directory not emptyIt seems this is due to the fact that the system detects that you're trying to create VMs with the same IDs.
I had success doing the following:
Code:
# systemctl stop pve-cluster
# pmxcfs -l
# cp -R old new
cp: cannot create regular file 'new/qemu-server/100.conf': File exists
# cp old/qemu-server/100.conf new/qemu-server/200.conf # do this for every VM
# mv old /root/ # for backup
# reboot
# systemctl stop pve-cluster
# pmxcfs -l
# cd /etc/pve/nodes/new/qemu-server
# mv 200.conf 100.conf # do this for every VM
# rebootSlightly involved, but does the trick. Also, I'm not sure if it's necessary to stop the pve-cluster service, manually mount the fuse fs and then reboot.
I did it anyway for reasons of caution.
Last edited:
the wiki does say "This must be done on a empty node." at least it does at the time of writing.
best way i know of (fresh install, before first boot):
- uncheck automatically reboot after successful install,
- ALT+<Fkey> when its done for a command line
- nano the files:
- reboot
- (restore your containers from backups?)
best way i know of (fresh install, before first boot):
- uncheck automatically reboot after successful install,
- ALT+<Fkey> when its done for a command line
- nano the files:
Code:
nano /etc/hosts /etc/hostname- reboot
- (restore your containers from backups?)
Am I correct that changing the hostname in a cluster setup with existing VMs would break the entire installation? Or is it somehow possible to change it by editing the SQLite DB directly?
Reason being that when I initially setup the cluster, our naming convention wasn't finalized yet. Can change it on all other hosts, so just the PVE hosts would remain with the old naming scheme...
Reason being that when I initially setup the cluster, our naming convention wasn't finalized yet. Can change it on all other hosts, so just the PVE hosts would remain with the old naming scheme...