Cluster cleanup after moving a server to a different ip.

ABaum

Member
Nov 2, 2018
11
0
6
45
I have a 3 node cluster running and it is quorate.
I can do pass wordless ssh without errors to and from each node.
however the web GUI still wants to use a old ip address to connect the console and do replication.

Can anyone point me to the right files to correct this problem?

Thanks

Andrwe
 
Have you updated the entry in /etc/hosts with the new IP?
 
yes I did
I put all the local addresses in for the cluster network.
/etc/hosts

Code:
127.0.0.1 localhost.localdomain localhost
192.168.2.3 pve21
192.168.2.2 pve3
192.168.2.1 pve19

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
 
I found this but I doubt I should change this by hand.
however is shows the incorrect ip address for the pve21

/etc/pve/.members

Code:
{
"nodename": "pve21",
"version": 23,
"cluster": { "name": "ANDREW", "version": 4, "nodes": 3, "quorate": 1 },
"nodelist": {
  "pve19": { "id": 1, "online": 1, "ip": "192.168.2.1"},
  "pve21": { "id": 3, "online": 1, "ip": "192.168.15.4"},
  "pve3": { "id": 2, "online": 1, "ip": "192.168.2.2"}
  }
}
 
Where exactly did you update the IP?
In /etc/network/interfaces, /etc/hosts and /etc/pve/corosync.conf?
 
those are correct on all three nodes.
however when I joined pve21 to the cluster pve21 had a static ip of 192.168.15.4 on vmbr0 and in hosts had the same ip.
I joined the cluster using vmbr6 with static of 192.168.2.3
this is how interfaces looks now.

root@pve21:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet manual

auto vmbr0
iface vmbr0 inet dhcp
bridge-ports eno1
bridge-stp off
bridge-fd 0

auto vmbr1
iface vmbr1 inet dhcp
bridge-ports eno2
bridge-stp off
bridge-fd 0

auto vmbr6
iface vmbr6 inet static
address 192.168.2.3/24
bridge-ports none
bridge-stp off
bridge-fd 0
 
Hello
Sorry for the bother.
a simple reboot of the unreachable node fixed the problem
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!