VTN Manager Neutron try to create a bridge even when an OVSDB node is disconnected

When I made an OVSDB node disconnected to OpenDaylight controller with VTN Manager Neutron running, I saw the following INFO message in the karaf.log.

2016-02-11 07:55:27,099 | INFO | (snip) 0.4.0.SNAPSHOT | Bridge Added: true

Reading the source code of the VTN Manager Neutron, it seems to me that the VTN Manager Neutron try to create a bridge even when an OVSDB node gets disconnected to the controller.
Though, I think it should create a bridge (br-int) only when it detects a new OVSDB node connected.

What I used
===========

The latest code on the stable/beryllium branch of VTN project on 11th February, 2016.

$ git log -3 --oneline
fe58092 Merge "VTN-89: Fixed Port map configuration with OpenStack Liberty" into stable/beryllium
2a40eb5 Merge "VTN-110: Fixed FT scripts in VTN Coordinator" into stable/beryllium
28ebb41 VTN-116: Fixed UT for ODCdriver in VTN Coordinator

How to reproduce the issue
==========================

Repeat to make an OVSDB node connected and disconnected to OpenDaylight controler.

1. sudo ovs-vsctl show

6f414672-bca6-47b8-93e6-5b40925bc934
Manager "tcp:127.0.0.1:6640"
ovs_version: "2.3.1"

2. sudo ovs-vsctl set-manager tcp:192.168.2.62:6640
(Make the OVSDB node connected.)

3. sudo ovs-vsctl show

6f414672-bca6-47b8-93e6-5b40925bc934
Manager "tcp:192.168.2.62:6640"
is_connected: true
ovs_version: "2.3.1"

4. sudo ovs-vsctl set-manager tcp:127.0.0.1:6640
(Make the OVSDB node disconnected.)

Here 192.168.2.62 is the IP address of the OpenDaylight controller.