[OVSDB-185] br-int is not getting created with lithium 0.3.0 snapshot Created: 09/Jul/15  Updated: 08/Feb/16  Resolved: 08/Feb/16

Status: Resolved
Project: ovsdb
Component/s: API
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Ravi Shankar S Assignee: Marcus G K Williams
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: Text File OVS-logs.txt     Text File karaf.log    
External issue ID: 3974

 Description   

Issue:
The br-int bridge is not automatically created with Lithium 0.3.0 snapshot controller, when manager connection is established at port 6640.

Steps:
1. Run the lithium 0.3.0 controller by installing the below features
a. odl-ovsdb-openstack
b. odl-dlux-core

2. After the controller is initialzed set the manager connection using the below command.
sudo ovs-vsctl set-manager tcp:<controller_ip>:6640

[ravi@localhost distribution-karaf-0.3.0-Lithium]$ sudo ovs-vsctl show
0c68e562-340d-4dac-8bd5-33cc61838d4a
Manager "tcp:10.16.130.215:6640"
is_connected: true
ovs_version: "2.3.2"

After executing the set-manager, br-int was not created automatically. Because of the failure to create br-int, the openflow connection is also not getting connected.

 Comments   
Comment by Ravi Shankar S [ 09/Jul/15 ]

Attachment karaf.log has been added with description: Karaf logs

Comment by Ravi Shankar S [ 09/Jul/15 ]

Attachment OVS-logs.txt has been added with description: OVS logs

Comment by Marcus G K Williams [ 11/Aug/15 ]

Attempting to reproduce this bug.

Comment by Ravi Shankar S [ 12/Aug/15 ]

I have tested this issue with the ODL-Li release (ODL_mode=manual/external-odl) + devstack kilo release. In this setup the issue is seen very rarely.

Comment by Michal Skalski [ 14/Sep/15 ]

See the same symptoms when using ODL 0.3.1 SR1 with OpenStack Juno and OVS 2.3.1.
It actually happen quite often, in two different ways:

1. just after adding manager br-int is not created

2. after while everything was set up correctly and br-in was created, the connection with manager is lost:

015-09-14T20:49:44.328Z|00007|reconnect|ERR|tcp:192.168.0.2:6640: no response to inactivity probe after 5.83 seconds, disconnecting
2015-09-14T20:49:44.328Z|00008|reconnect|INFO|tcp:192.168.0.2:6640: connection dropped
2015-09-14T20:50:14.233Z|00009|reconnect|INFO|tcp:192.168.0.2:6640: connecting...
2015-09-14T20:50:14.233Z|00010|reconnect|INFO|tcp:192.168.0.2:6640: connected

and after that ovs no longer has br-int bridge.

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