https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/VTN-118 vtn <p>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.</p> <p> 2016-02-11 07:55:27,099 | INFO | (snip) 0.4.0.SNAPSHOT | Bridge Added: true</p> <p>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.<br/> Though, I think it should create a bridge (br-int) only when it detects a new OVSDB node connected.</p> <p>What I used<br/> ===========</p> <p>The latest code on the stable/beryllium branch of VTN project on 11th February, 2016.</p> <p>$ git log -3 --oneline<br/> fe58092 Merge "<a href="https://jira.opendaylight.org/browse/VTN-89" title="Port mapping was not configured with OpenStack Liberty" class="issue-link" data-issue-key="VTN-89"><del>VTN-89</del></a>: Fixed Port map configuration with OpenStack Liberty" into stable/beryllium<br/> 2a40eb5 Merge "<a href="https://jira.opendaylight.org/browse/VTN-110" title="Change in VTN Coordinator FT files due to RESTCONF implementation in VTN Manager" class="issue-link" data-issue-key="VTN-110"><del>VTN-110</del></a>: Fixed FT scripts in VTN Coordinator" into stable/beryllium<br/> 28ebb41 <a href="https://jira.opendaylight.org/browse/VTN-116" title="Enabling UT for ODCdriver module in VTN Coordinator" class="issue-link" data-issue-key="VTN-116"><del>VTN-116</del></a>: Fixed UT for ODCdriver in VTN Coordinator</p> <p>How to reproduce the issue<br/> ==========================</p> <p>Repeat to make an OVSDB node connected and disconnected to OpenDaylight controler.</p> <p> 1. sudo ovs-vsctl show</p> <p> 6f414672-bca6-47b8-93e6-5b40925bc934<br/> Manager "tcp:127.0.0.1:6640"<br/> ovs_version: "2.3.1"</p> <p> 2. sudo ovs-vsctl set-manager tcp:192.168.2.62:6640<br/> (Make the OVSDB node connected.)</p> <p> 3. sudo ovs-vsctl show</p> <p> 6f414672-bca6-47b8-93e6-5b40925bc934<br/> Manager "tcp:192.168.2.62:6640"<br/> is_connected: true<br/> ovs_version: "2.3.1"</p> <p> 4. sudo ovs-vsctl set-manager tcp:127.0.0.1:6640<br/> (Make the OVSDB node disconnected.)</p> <p>Here 192.168.2.62 is the IP address of the OpenDaylight controller.</p> <p>Operating System: All<br/> Platform: All</p> VTN-118

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

Bug Resolved Done Ananthi Palaniswamy Hideyuki Tai Thu, 11 Feb 2016 22:49:46 +0000 Tue, 15 Mar 2016 04:35:33 +0000 Tue, 15 Mar 2016 04:35:33 +0000 unspecified VTN Manager 0 2 <p>Patch Merged to Master: <a href="https://git.opendaylight.org/gerrit/#/c/35661/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/35661/</a><br/> Patch Merged to stable/Be: <a href="https://git.opendaylight.org/gerrit/#/c/35688/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/35688/</a></p> <p>Tested in the latest source and verified the behavior.</p> <p>1. Launched VTN</p> <p>2. OVSDB <br/> gvrangan@openstack-controlnode:~/devstack$ sudo ovs-vsctl show<br/> 3480f0c7-8a7b-41bc-a090-73854002680d<br/> ovs_version: "2.3</p> <p>3. Set ODL as Manager for OVS<br/> sudo ovs-vsctl set-manager tcp:10.128.0.2:6640</p> <p>4. VTN Manager neutron implementation creates the br-int as expected</p> <p> gvrangan@openstack-controlnode:~/devstack$ sudo ovs-vsctl show<br/> 3480f0c7-8a7b-41bc-a090-73854002680d<br/> Manager "tcp:10.128.0.2:6640"<br/> is_connected: true<br/> Bridge br-int<br/> Controller "tcp:10.128.0.2:6653"<br/> is_connected: true<br/> fail_mode: secure<br/> Port br-int<br/> Interface br-int<br/> type: internal<br/> Port "eth1"<br/> Interface "eth1"<br/> ovs_version: "2.3.2"</p> <p>5. Del Manager in OVS and delete the bridge</p> <p>6. set manager again and the br-int is created once again. <br/> gvrangan@openstack-controlnode:~/devstack$ sudo ovs-vsctl set-manager tcp:10.128.0.2:6640<br/> gvrangan@openstack-controlnode:~/devstack$ <br/> gvrangan@openstack-controlnode:~/devstack$ sudo ovs-vsctl show<br/> 3480f0c7-8a7b-41bc-a090-73854002680d<br/> Manager "tcp:10.128.0.2:6640"<br/> Bridge br-int<br/> Controller "tcp:10.128.0.2:6653"<br/> fail_mode: secure<br/> Port br-int<br/> Interface br-int<br/> type: internal<br/> Port "eth1"<br/> Interface "eth1"<br/> ovs_version: "2.3.2"</p> <p>7. Earlier, After adding again, the br-int was not getting created,</p> Development External issue ID 5330 External issue URL Rank 0|i02tp3: