REVIEW: https://review.gluster.org/17255 (common-ha: adding a node to existing cluster failed to start pacemaker) posted (#1) for review on release-3.10 by Kaleb KEITHLEY (kkeithle)
REVIEW: https://review.gluster.org/17255 (common-ha: adding a node to existing cluster failed to start pacemaker) posted (#2) for review on release-3.10 by Kaleb KEITHLEY (kkeithle)
COMMIT: https://review.gluster.org/17255 committed in release-3.10 by Kaleb KEITHLEY (kkeithle) ------ commit bbd891a942f25b59d5dce188e22de2debccfd0a8 Author: Kaleb S. KEITHLEY <kkeithle> Date: Thu May 11 09:16:34 2017 -0400 common-ha: adding a node to existing cluster failed to start pacemaker `pcs cluster start` in add_node() needs to wait for SSL certs to propagate, etc. -- just like setup. Change-Id: I44876305630a82e471824c085ed9ac58df08caa2 BUG: 1450053 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Reviewed-on: https://review.gluster.org/17255 Reviewed-by: soumya k <skoduri> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: jiffin tony Thottan <jthottan>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.3, please open a new bug report. glusterfs-3.10.3 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-June/031399.html [2] https://www.gluster.org/pipermail/gluster-users/