Comment 2 for bug 1332534

I've reproduced this on a virtual environment. So, here is how OVS bond got configured in my case on 3 controllers:

node-1 (10.108.4.3/24)
slave eth3: enabled
        active slave
        may_enable: true

node-2 (10.108.4.3/24)
slave eth4: enabled
        active slave
        may_enable: true

node-3 (10.108.4.4/24)
slave eth4: enabled
        active slave
        may_enable: true

node-2 and node-3 have eth4 as active bond slave. And they can access each other via bond interface:

[root@node-3 ~]# ping 10.108.4.4
PING 10.108.4.4 (10.108.4.4) 56(84) bytes of data.
64 bytes from 10.108.4.4: icmp_seq=1 ttl=64 time=0.026 ms
64 bytes from 10.108.4.4: icmp_seq=2 ttl=64 time=0.039 ms

But they can't ping node-1, because node-1 has different interface (eth3) as active bond slave:

[root@node-3 ~]# ping 10.108.4.2
PING 10.108.4.2 (10.108.4.2) 56(84) bytes of data.
From 10.108.4.4 icmp_seq=2 Destination Host Unreachable
From 10.108.4.4 icmp_seq=3 Destination Host Unreachable
From 10.108.4.4 icmp_seq=4 Destination Host Unreachable

[root@node-4 ~]# ping 10.108.4.2
PING 10.108.4.2 (10.108.4.2) 56(84) bytes of data.
From 10.108.4.4 icmp_seq=2 Destination Host Unreachable
From 10.108.4.4 icmp_seq=3 Destination Host Unreachable
From 10.108.4.4 icmp_seq=4 Destination Host Unreachable

Interconnection between node-1 and other controllers starts working as soon as we set active slave to the same interface on all controllers:

[root@node-1 ~]# ovs-appctl bond/set-active-slave ovs-bond0 eth4
done

[root@node-1 ~]# ping 10.108.2.4
PING 10.108.2.4 (10.108.2.4) 56(84) bytes of data.
64 bytes from 10.108.2.4: icmp_seq=1 ttl=64 time=1256 ms
64 bytes from 10.108.2.4: icmp_seq=2 ttl=64 time=256 ms
64 bytes from 10.108.2.4: icmp_seq=3 ttl=64 time=0.206 ms

[root@node-2 ~]# ping 10.108.4.2
PING 10.108.4.2 (10.108.4.2) 56(84) bytes of data.
64 bytes from 10.108.4.2: icmp_seq=1 ttl=64 time=0.472 ms
64 bytes from 10.108.4.2: icmp_seq=2 ttl=64 time=0.168 ms

I'm marking this bug as invalid, because this is environment configuration issue. In order to test NIC bonging, virtual or HW environment should be configured accordingly (it should support bonding for appropriate interfaces on a switch side).