-
Notifications
You must be signed in to change notification settings - Fork 94
Description
On ubuntu 24.04, crmsh is version 4.6.0-1ubuntu2.
Corosync: 3.1.7-1ubuntu3
Pacemaker: 2.1.6-5ubuntu2
From my (anonymized) configuration /etc/corosync/corosync.conf:
transport: udp
...
interface: {
bindnetaddr: 192.168.0.0
}
...
nodelist {
node {
ring0_addr: 192.168.0.50
name: machine1
id: 1
}
node {
ring0_addr: 192.168.0.51
name: machine2
id: 2
}
node {
ring0_addr: 192.168.0.52
name: machine3
id: 3
}
}
However, my /etc/hosts looks like this:
10.0.0.1 machine1
10.0.0.2 machine2
10.0.0.3 machine3
The corosync/pacemaker cluster communicates with their nodes over 192.168.0.0/24 and other services over a different internal network. This allows for clean iptable rules, separating traffic.
Am I right in thinking that what is happening is that first the software sees "machine1", checks /etc/hosts, sees 10.0.0.1 and tries connecting to the node via that IP? (which will be blocked by the firewall in my case)
And then after 2 minutes it gives up and tries ring0_addr? And if so, is there a way to rely on ring0_addr instead?
Or is something else going on?
I'm now waiting 2 minutes for an IP address resource to swap to a different host, that's my issue here.