[VTN-118] VTN Manager Neutron try to create a bridge even when an OVSDB node is disconnected Created: 11/Feb/16  Updated: 15/Mar/16  Resolved: 15/Mar/16

Status: Resolved
Project: vtn
Component/s: VTN Manager
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Hideyuki Tai Assignee: Ananthi Palaniswamy
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 5330

 Description   

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.

 Comments   
Comment by Venkatrangan Govindarajan [ 15/Mar/16 ]

Patch Merged to Master: https://git.opendaylight.org/gerrit/#/c/35661/
Patch Merged to stable/Be: https://git.opendaylight.org/gerrit/#/c/35688/

Tested in the latest source and verified the behavior.

1. Launched VTN

2. OVSDB
gvrangan@openstack-controlnode:~/devstack$ sudo ovs-vsctl show
3480f0c7-8a7b-41bc-a090-73854002680d
ovs_version: "2.3

3. Set ODL as Manager for OVS
sudo ovs-vsctl set-manager tcp:10.128.0.2:6640

4. VTN Manager neutron implementation creates the br-int as expected

gvrangan@openstack-controlnode:~/devstack$ sudo ovs-vsctl show
3480f0c7-8a7b-41bc-a090-73854002680d
Manager "tcp:10.128.0.2:6640"
is_connected: true
Bridge br-int
Controller "tcp:10.128.0.2:6653"
is_connected: true
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "eth1"
Interface "eth1"
ovs_version: "2.3.2"

5. Del Manager in OVS and delete the bridge

6. set manager again and the br-int is created once again.
gvrangan@openstack-controlnode:~/devstack$ sudo ovs-vsctl set-manager tcp:10.128.0.2:6640
gvrangan@openstack-controlnode:~/devstack$
gvrangan@openstack-controlnode:~/devstack$ sudo ovs-vsctl show
3480f0c7-8a7b-41bc-a090-73854002680d
Manager "tcp:10.128.0.2:6640"
Bridge br-int
Controller "tcp:10.128.0.2:6653"
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "eth1"
Interface "eth1"
ovs_version: "2.3.2"

7. Earlier, After adding again, the br-int was not getting created,

Generated at Wed Feb 07 20:48:05 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.