[OVSDB-341] OVS and ietf interface holds tunnel information even after ITM is deleted via REST. Created: 24/May/16  Updated: 30/Oct/17  Resolved: 28/Jun/16

Status: Resolved
Project: ovsdb
Component/s: Southbound.Open_vSwitch
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: vidya sathyanarayanachar Assignee: Vishal Thapar
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: Zip Archive karaf.zip     File log.rar     Text File odl master deletion TR.txt     Text File screen-karaf.log    
External issue ID: 5945
Priority: Highest

 Description   

Manually ITM is created and when deleted manually via REST using url : http://10.183.254.160:8181/restconf/config/itm:transport-zones/transport-zone/zone name/ its observed that , even after deletion , the ietf interface operational , network topology operational and OVS retain tunnel information as seen in the dump.
The similar case is seen in Automation also. PFA of the logs with Url dumps and the Karaf log .

the build tested is for ODL master - distribution-karaf-0.5.0-20160522.153800-2438.tar.gz downloaded from - https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.5.0-SNAPSHOT/ .

 Comments   
Comment by vidya sathyanarayanachar [ 24/May/16 ]

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

Comment by vidya sathyanarayanachar [ 24/May/16 ]

this file has the url dumps .

Comment by vidya sathyanarayanachar [ 24/May/16 ]

Attachment odl master deletion TR.txt has been added with description: Url dumps

Comment by Faseela K [ 03/Jun/16 ]

logs with ovsdb debugs enabled

Comment by Faseela K [ 03/Jun/16 ]

Attachment log.rar has been added with description: ovsdb debug logs

Comment by Faseela K [ 03/Jun/16 ]

Hi Anil,
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
Thanks,
Faseela

Comment by Vishal Thapar [ 03/Jun/16 ]

@Faseela: Since these logs are from different run, would help to have the interfaces [optional] and ovsdb config datastore information, before and after delete. Or at very least, tunnel being created and on which bridge and node.

Comment by Vishal Thapar [ 15/Jun/16 ]

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 [switch initiated connection] yet the IID is incorrectly setup as if it is ODL initiated connection:

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
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
2016-06-15 13:49:58,040 | INFO | nectionService-5 | OvsdbConnectionManager | 267 - org.opendaylight.ovsdb.southbound-impl - 1.3.0.SNAPSHOT | InstanceIdentifier KeyedInstanceIdentifier

{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]]]]}

generated for device connection ConnectionInfo [Remote-address=192.168.56.111, Remote-port=56739, Local-address192.168.56.1, Local-port=6640, type=PASSIVE]
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[

{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=ovsdb:1}

]/node/node[

{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)node-id=ovsdb://192.168.56.111:6640}

]} is registered for ownership.

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.

Comment by Alon Kochba [ 20/Jun/16 ]

Attachment screen-karaf.log has been added with description: karaf log

Comment by Alon Kochba [ 20/Jun/16 ]

Confirmed that tunnels are NOT configured by OVSDB after adding VTEP via REST.
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.

Using latest Boron snapshot - distribution-karaf-0.5.0-20160619.213912-3029.zip

Comment by Vishal Thapar [ 22/Jun/16 ]

Patch: https://git.opendaylight.org/gerrit/#/c/40697/

Comment by vidya sathyanarayanachar [ 24/Jun/16 ]

The fix provided is working fine as seen in the log results.

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