I have a two-node cluster; been running for almost a year. New node configured; time to add it.
(All are running the same PVE version; all have same underlying linux; all can ssh to one another; etc etc.)
I used the GUI to add the new node to the cluster (pasting the blob of secure info). The process began just fine, but got stuck at:
I went looking for the issue... for the most part it appears that the node-add worked just fine!
* GUI datacenter on all three nodes shows all three
*
* corosync.conf is identical across the board
There are two semi-strange things, which I have no idea about:
Pete
(All are running the same PVE version; all have same underlying linux; all can ssh to one another; etc etc.)
I used the GUI to add the new node to the cluster (pasting the blob of secure info). The process began just fine, but got stuck at:
stopping pve-cluster serviceI went looking for the issue... for the most part it appears that the node-add worked just fine!
* GUI datacenter on all three nodes shows all three
*
pvecm status shows all three are active* corosync.conf is identical across the board
There are two semi-strange things, which I have no idea about:
- In
pvecm statusthe new node status is "nr" -- not registered.
I find no documentation on what that means and how to fix it (assuming a fix is needed at all!)
- One of the existing nodes is now running its cluster membership NIC at 100mbit on a cat6 cable. I haven't noticed such an anomaly before, not that I was looking
- Is a "not registered" cluster member an issue? (If so, what changes this status?)
- Is the cluster-node-add GUI "hang" just a visual anomaly? Where do I look for further insight?
Pete