Comment 11 for bug 1471647

According to info you provided you do not have problems with networking
crm status
Last updated: Mon Jul 6 14:57:46 2015
Last change: Mon Jul 6 04:16:17 2015
Stack: corosync
Current DC: node-16.domain.tld (16) - partition with quorum
Version: 1.1.12-561c4cf
3 Nodes configured
34 Resources configured

Online: [ node-13.domain.tld node-16.domain.tld node-17.domain.tld ]

Above means that all is ok, traffic goes via bond. Pacemaker cluster uses management network which is on bond0, vlan 3.

One thing I see here that first time connectivity_tests.pp task have not been applied
but then looks like was second turn (re-deploy) and success

I also see that post deployment tasks have not been applied to any controller that means that deployment failed and that is why I have partitioning.

Now only logs from directory /var/log/docker-logs/ on master node can help us

About diagnostic snapshot - the easiest way to do it is to fire the command
[root@nailgun ~]# fuel snapshot
Generating dump...
Downloading: http://127.0.0.1:8000/dump/fuel-snapshot-2015-07-07_11-18-08.tar.xz Bytes: 135969364
[==============================================================================]()
[root@nailgun ~]# ls -la fuel-snapshot-2015-07-07_11-18-08.tar.xz
-rw-r--r-- 1 root root 135969364 Jul 7 11:20 fuel-snapshot-2015-07-07_11-18-08.tar.xz

and upload it to us

It also is available via FUEL Web UI on the support tab Download Diagnostic Snapshot

if you are experiencing the problems with generating diagnostic snapshot please provide the logs from the directory /var/log/docker-logs/ on master node.

Thanks.