ha-cluster-join bootstrap script error "cluster.join: not enough values to unpack (expected 3, got 1)"

This document (000019902) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise High Availability Extension 15 SP2

Situation

The first cluster node (e.g. "node1" with IP address 192.168.0.101) is setup successfully using the "ha-cluster-init" bootstrap script.

But adding the second cluster node (e.g. "node2" with IP address 192.168.0.102) using the "ha-cluster-join" bootstrap script encounter errors.
For example:
node2:~ # ha-cluster-join -c 192.168.0.101
ERROR: cluster.join: not enough values to unpack (expected 3, got 1)

Resolution

1. Remove the node information for "node2" from "/etc/corosync/corosync.conf" inside "node1".

For example, before change:
node {
ring0_addr: 192.168.0.101
nodeid: 1
}
node {
ring0_addr: 192.168.0.102
nodeid: 2
}

After change:
node {
ring0_addr: 192.168.0.101
nodeid: 1
}

2. Sync the changes to "node2" by running "csync2" command in "node1":
node1:~ # csync2 -xv

3. Restart "corosync.service" in "node1":
node1:~ # systemctl restart corosync.service

4. Run the "ha-cluster-join" bootstrap script in "node2":
node2:~ # ha-cluster-join -c 192.168.0.101

5. "node2" should be able to join "node1" in the cluster now.

Cause

After repeated failed attempts to setup the cluster nodes, the "/etc/corosync/corosync.conf" configuration is no longer in a clean state.
The node information for the second node must be cleaned up from the "/etc/corosync/corosync.conf" before running "ha-cluster-join" bootstrap script again.

Status

Reported to Engineering

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.