Emilien saw that /etc/sysconfig/clustercheck file is not created on controller-0, while it seems to be created on other nodes controller-1 and controller-2.

wget http://logs.openstack.org/23/404223/4/check-tripleo/gate-tripleo-ci-centos-7-ovb-ha/8bfb546/logs/overcloud-controller-1/var/log/messages -O- 2>/dev/null | grep -F 'clustercheck' | tail -1
Nov 29 15:34:01 localhost os-collect-config: #033[mNotice: /Stage[main]/Tripleo::Profile::Pacemaker::Database::Mysql/Exec[create-root-sysconfig-clustercheck]/returns: executed successfully#033[0m

So it seems something interrupted the deploy. Could it be related to loss of quorum which is getting in the way?:

# wget http://logs.openstack.org/23/404223/4/check-tripleo/gate-tripleo-ci-centos-7-ovb-ha/8bfb546/logs/overcloud-controller-1/var/log/messages -O- 2>/dev/null | grep QUORUM 
Nov 29 15:32:00 localhost corosync[26839]: [QUORUM] This node is within the non-primary component and will NOT provide any services.
Nov 29 15:32:00 localhost corosync[26839]: [QUORUM] Members[1]: 2
Nov 29 15:32:23 localhost corosync[26839]: [QUORUM] This node is within the primary component and will provide service.
Nov 29 15:32:23 localhost corosync[26839]: [QUORUM] Members[3]: 2 3 1

Although it seems quorum got recovered, this is never a good sigh and should not happen in the first place. A few seconds after this quorum log, I see the first suspicious log related to connections:

Nov 29 15:32:32 localhost os-collect-config: sure: created\u001b[0m\n\u001b[mNotice: /Stage[main]/Haproxy/Haproxy::Instance[haproxy]/Haproxy::Config[haproxy]/Concat[/etc/haproxy/haproxy.cfg]/File[/etc/haproxy/haproxy.cfg]/content: content changed '{md5}1f337186b0e1ba5ee82760cb437fb810' to '{md5}fe996ee969512d62439f8ed86b2490fc'\u001b[0m\n\u001b[mNotice: /Stage[main]/Haproxy/Haproxy::Instance[haproxy]/Haproxy::Config[haproxy]/Concat[/etc/haproxy/haproxy.cfg]/File[/etc/haproxy/haproxy.cfg]/seluser: seluser changed 'unconfined_u' to 'system_u'\u001b[0m\n\u001b[mNotice: /Stage[main]/Tripleo::Profile::Base::Haproxy/Exec[haproxy-reload]: Triggered 'refresh' from 1 events\u001b[0m\n\u001b[mNotice: Applied catalog in 115.75 seconds\u001b[0m\n", "deploy_stderr": "exception: connect failed\n\u001b[1;33mWarning: This method is deprecated, please use match expressions with Stdlib::Compat::Array instead. They are described at https://docs.puppet.com/puppet/latest/reference/lang_data_type.html#match-expressions.\n   (at /etc/puppet/modules/stdlib/lib/puppet/functions/deprecation.rb:19:in `deprecation')\u001b[0m\n\u001b[1;33mWarning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Hash. There is further documentation for validate_legacy function in the README.\n   (at /etc/puppet/modules/stdlib/lib/puppet/functions/deprecation.rb:19:in `deprecation')\u001b[0m\n\u001b[1;33mWarning: ModuleLoader: module 'mysql' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n   (file & line not available)\u001b[0m\n\u001b[1;33mWarning: ModuleLoader: module 'rabbitmq' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\n   (file & line not available)\u001b[0m\n\u001b[1;33mWarning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Bool. There is further documentation for validate_legacy function in the README.\n   (at /etc/puppe