Setup corosync/pacemaker on db3
corosync/pacemaker is not running properly on db3. First it refused to add the new node to its nodelist, requiring me to manually add it to the file and run chef-client
. Now that it's technically running it's only seeing db3 (itself), not db1 and db2. db1 and db2 in turn don't see db3. All 3 hosts have the same authorization key and configuration, so I'm not sure what's going on.
cc @gl-infra