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/OVSDB-341 ovsdb <p>Manually ITM is created and when deleted manually via REST using url : <a href="http://10.183.254.160:8181/restconf/config/itm:transport-zones/transport-zone/zone" class="external-link" target="_blank" rel="nofollow noopener">http://10.183.254.160:8181/restconf/config/itm:transport-zones/transport-zone/zone</a> name/ its observed that , even after deletion , the ietf interface operational , network topology operational and OVS retain tunnel information as seen in the dump.<br/> The similar case is seen in Automation also. PFA of the logs with Url dumps and the Karaf log .</p> <p>the build tested is for ODL master - distribution-karaf-0.5.0-20160522.153800-2438.tar.gz downloaded from - <a href="https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.5.0-SNAPSHOT/" class="external-link" target="_blank" rel="nofollow noopener">https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.5.0-SNAPSHOT/</a> .</p> <p>Operating System: All<br/> Platform: All</p> OVSDB-341

OVS and ietf interface holds tunnel information even after ITM is deleted via REST.

Bug Resolved Done Vishal Thapar vidya sathyanarayanachar Tue, 24 May 2016 06:32:32 +0000 Mon, 30 Oct 2017 19:52:46 +0000 Tue, 28 Jun 2016 06:46:03 +0000 unspecified Southbound.Open_vSwitch 0 4 <p>Attachment karaf.zip has been added with description: Karaf log</p> <p>this file has the url dumps .</p> <p>Attachment odl master deletion TR.txt has been added with description: Url dumps</p> <p>logs with ovsdb debugs enabled</p> <p>Attachment log.rar has been added with description: ovsdb debug logs</p> <p>Hi Anil,<br/> TEP delete issue is again seen on boron, topology config DS is deleted, however TEP is not deletd from switch. See the ovsdb debug log attachment for more info<br/> Thanks,<br/> Faseela</p> <p>@Faseela: Since these logs are from different run, would help to have the interfaces <span class="error">&#91;optional&#93;</span> and ovsdb config datastore information, before and after delete. Or at very least, tunnel being created and on which bridge and node.</p> <p>Facing a different issue when trying to reproduce on master, tunnel creation itself is failing. I did the build hour ago so should have latest code. Also, noticed something curious when adding device. I did set-manager from switch <span class="error">&#91;switch initiated connection&#93;</span> yet the IID is incorrectly setup as if it is ODL initiated connection:</p> <p>2016-06-15 13:49:58,017 | INFO | nectionService-5 | OvsdbConnectionManager | 267 - org.opendaylight.ovsdb.southbound-impl - 1.3.0.SNAPSHOT | Library connected PASSIVE from /192.168.56.111:56739 to /192.168.56.1:6640<br/> 2016-06-15 13:49:58,018 | INFO | nectionService-5 | OvsdbConnectionManager | 267 - org.opendaylight.ovsdb.southbound-impl - 1.3.0.SNAPSHOT | OVSDB Connection from /192.168.56.111:56739<br/> 2016-06-15 13:49:58,040 | INFO | nectionService-5 | OvsdbConnectionManager | 267 - org.opendaylight.ovsdb.southbound-impl - 1.3.0.SNAPSHOT | InstanceIdentifier KeyedInstanceIdentifier</p> {targetType=interface org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.topology.Node, path=[org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.NetworkTopology, org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology[key=TopologyKey [_topologyId=Uri [_value=ovsdb:1]]], org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.topology.Node[key=NodeKey [_nodeId=Uri [_value=ovsdb://192.168.56.111:6640]]]]} <p> generated for device connection ConnectionInfo <span class="error">&#91;Remote-address=192.168.56.111, Remote-port=56739, Local-address192.168.56.1, Local-port=6640, type=PASSIVE&#93;</span><br/> 2016-06-15 13:49:58,040 | INFO | nectionService-5 | OvsdbConnectionManager | 267 - org.opendaylight.ovsdb.southbound-impl - 1.3.0.SNAPSHOT | OVSDB entity Entity{type='ovsdb', id=/(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[</p> {(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=ovsdb:1} <p>]/node/node[</p> {(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)node-id=ovsdb://192.168.56.111:6640} <p>]} is registered for ownership.</p> <p>Tunnels configuration shows up in ConfigDS but not in switch. This looks similar to behavior Anil had fixed earlier. Looks like recent change to DTCL and related fixes have broken it.</p> <p>Attachment screen-karaf.log has been added with description: karaf log</p> <p>Confirmed that tunnels are NOT configured by OVSDB after adding VTEP via REST.<br/> Tunnel termination points are added to config DS, but are NOT added to the OVS via OVSDB and thus are not added to operational DS.</p> <p>Using latest Boron snapshot - distribution-karaf-0.5.0-20160619.213912-3029.zip</p> <p>Patch: <a href="https://git.opendaylight.org/gerrit/#/c/40697/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/40697/</a></p> <p>The fix provided is working fine as seen in the log results.</p> Development External issue ID 5945 External issue URL Issue Type Priority Rank 0|i0224v: