Containers with question marks when renaming Node

[billybob]

Renaming a node (modifying /etc/hosts, /etc/hostname) causes the following issues (see attached):

• Both old & the new node names show in the Web GUI
• Under old node name, all LXC containers show with a question mark
• Under new node, none of the VMs & containers show up.

If I manually try to copy /etc/pve/nodes/pve1/lxc to /etc/pve/nodes/pxmx1/lxc, I get the error from the command eventhough the target directory does not have any files.

 

[datschlatscher]

Renaming a node in a cluster can be a bit finicky, it seems you forgot to change the corosync config which is linked at the very bottom of the renaming a node page.
The problems you are experiencing here are most likely from the desynchronized corosync configurations. Following the steps documented in the link above should resolve these issues.

 

[billybob]

Renaming a node in a cluster can be a bit finicky, it seems you forgot to change the corosync config which is linked at the very bottom of the renaming a node page.
The problems you are experiencing here are most likely from the desynchronized corosync configurations. Following the steps documented in the link above should resolve these issues.

Thanks for your response.

Node is not participating in a cluster. This is a standard standalone node.

 

[datschlatscher]

Node is not participating in a cluster. This is a standard standalone node.

Sorry, I was thrown off by the picture you included because that looked like non-quorate cluster behaviour to me.

I could reproduce the same problem you were facing myself. It seems to stem from trying to rename a node that contains guests.

If I manually try to copy /etc/pve/nodes/pve1/lxc to /etc/pve/nodes/pxmx1/lxc, I get the error from the command eventhough the target directory does not have any files.

The pmxcfs (manages the /etc/pve directory) does not allow multiple guest configurations of the same id. Therefore copying the files does not work. Alternatively you can move the files to the lxc folder in the new node. This resolved the problem for me, you should be able to safely remove the node folder after that but I would advise you to make a backup just in case.