********** CLI Output *********** + pcs property set stonith-enabled=false Error: unable to get cib Error: unable to get cib + sleep 4 + pcs cluster start --all gqas014: Unable to connect to gqas014.sbu.lab.eng.bos.redhat.com (Connection error) gqas015: Unable to connect to gqas015.sbu.lab.eng.bos.redhat.com (Connection error) gqas009: Unable to connect to gqas009.sbu.lab.eng.bos.redhat.com (Connection error) gqas010: Unable to connect to gqas010.sbu.lab.eng.bos.redhat.com (Connection error) Error: unable to start all nodes cluster devels say this is the result of new async behavior of the `pcs cluster setup ...` command. SSL auth certs have to be deployed before the cluster will accept connections. They suggest a delay of approx 12 seconds between the `pcs cluster setup ...` and `pcs cluster start --all`
REVIEW: https://review.gluster.org/16690 (common-ha: unable to start HA, Connection Error) posted (#1) for review on release-3.9 by Kaleb KEITHLEY (kkeithle)
COMMIT: https://review.gluster.org/16690 committed in release-3.9 by Kaleb KEITHLEY (kkeithle) ------ commit 333dd916ebe645230c302fd9a1c2645c519b1d6d Author: Kaleb S. KEITHLEY <kkeithle> Date: Mon Feb 20 10:41:51 2017 -0500 common-ha: unable to start HA, Connection Error See BZ 1284404. pcsd behavior has changed and pcsd will not accept connections until SSL certificates have fully propagated throughout all the nodes HA devels suggest a 12 second delay between the `pcs cluster setup ...` and the `pcs cluster start --all` Change-Id: If94b6991a62f346dbead023c7e7f8282a995728c BUG: 1425110 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Reviewed-on: https://review.gluster.org/16690 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: soumya k <skoduri>
This bug is getting closed because GlusterFS-3.9 has reached its end-of-life [1]. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please open a new bug against the newer release. [1]: https://www.gluster.org/community/release-schedule/