wsrep_sst_xtrabackup-v2: joiner does not bind to specified address

[Sindarina]

The socat listener initiated by 'wsrep_sst_xtrabackup-v2' on the joining node does not bind to the specified bind address, leading to problems in tunnelling scenarios because it wants to bind to '0.0.0.0:4444' at all times. The socat client on the donor does not have this problem, and binds to the 'wsrep_node_address' specified in 'my.cnf'.

This is further complicated by a bug in the 'wsrep_sst_xtrabackup-v2' bash code that handles the passing of the socket options specified via 'sockopt'. When attempting to pass the 'wsrep_node_address' value to socat via 'bind=x.x.x.x', the joining node goes completely silent, and fails. Nothing appears in the MySQL error log at all.

When the bind socket option is hardcoded on line 231, the SST works like a charm, and the node joins without issues. I suspect that specifying the socket option as 'bind=${WSREP_SST_OPT_ADDR}' might work as well, as this yields the same address in this particular setup, but I haven't spent enough time with the bash code to be sure.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1321