MySQL doesn't set up in Full HA topology.

[Sagi (Sergey) Shnaidman]

MySQL fails to set up sometimes in Full HA installation: approx. in 30% of cases.
Galera couldn't connect to other peers.

root@control-server00:~# tail /var/log/mysql/error.log
140822 10:25:18 [ERROR] WSREP: gcs/src/gcs.c:gcs_open():1292: Failed to open channel 'my_wsrep_cluster' at 'gcomm://192.168.40.3,192.168.40.4,192.168.40.5': -110 (Connection timed out)
140822 10:25:18 [ERROR] WSREP: gcs connect failed: Connection timed out
140822 10:25:18 [ERROR] WSREP: wsrep::connect() failed: 7
140822 10:25:18 [ERROR] Aborting

All logs and configs are available here:
https://172.29.173.228:8080/full_ha/81/

[Chris Ricker (chris-ricker)]

It looks like you're bootstrapping wrong

etc0/mysql/my.cnf:wsrep_cluster_address = gcomm://192.168.40.3,192.168.40.4,192.168.40.5
etc1/mysql/my.cnf:wsrep_cluster_address = gcomm://192.168.40.3,192.168.40.4,192.168.40.5
etc2/mysql/my.cnf:wsrep_cluster_address = gcomm://192.168.40.3,192.168.40.4,192.168.40.5

first node should be gcomm:// until it's all working

once it comes up and is working, then bring up the others

once all 3 are up and talking, then change first node to gcomm://ip1,ip2,ip3

[Sagi (Sergey) Shnaidman (sshnaidm)]

It's a workaround, not solution.
Could it be configured so that you will not need to stop installation, enter boxes, change things, reinstall things, continue installation?
If no, then it's a bug (until it's documented as required manual steps of install).

BTW, why does it work in 60% other cases?

[Sagi (Sergey) Shnaidman (sshnaidm)]

P.S. If you set bug as incomplete, please specify which info exactly you expect from me.