Br-int is not created when an OVS is disconnected and then quickly re-connected to the 3-nodes ODL. The reproduction steps are below:

1) start 3-nodes cluster, say
10.138.0.2, 10.138.0.3, 10.138.0.4
2) connect an OVS switch to the cluster
ovs-vsctl set-manager tcp:10.138.0.2:6640 tcp:10.138.0.3:6640 tcp:10.138.0.4:6640
3) br-int is properly created at the OVS switch
Manager "tcp:10.138.0.2:6640"
Manager "tcp:10.138.0.3:6640"
Manager "tcp:10.138.0.4:6640"
Bridge br-int
Controller "tcp:10.138.0.2:6653"
is_connected: true
Controller "tcp:10.138.0.4:6653"
is_connected: true
Controller "tcp:10.138.0.3:6653"
is_connected: true
fail_mode: secure
Port br-int
Interface br-int
type: internal
ovs_version: "2.0.2"

4) delete the br-int, disconnect the OVS, and re-connect the OVS in quick succession, ie
ovs-vsctl del-br br-int; ovs-vsctl del-manager; ovs-vsctl set-manager tcp:10.138.0.2:6640 tcp:10.138.0.3:6640 tcp:10.138.0.4:6640

5) Intermittently (one out of 5 tries), the br-int is not created after the OVS is connected to the cluster:

0af0ec21-563d-40cf-900c-6a66ef91a34d
Manager "tcp:10.138.0.2:6640"
is_connected: true
Manager "tcp:10.138.0.3:6640"
is_connected: true
Manager "tcp:10.138.0.4:6640"
is_connected: true
ovs_version: "2.0.2"

When the issue in 5) happens there is no entry for the OVS connection in the operational DS. That means netvirt never gets the ADD node event to create teh br-int in the first place. The events for delete and create same node might have been clobbered each other.

I am testing with latest boron code as of Aug 30, 2016