[OPNFLWPLUG-75] No Flowmod sent when trying to delete all the flows in a table Created: 03/Mar/14 Updated: 27/Sep/21 Resolved: 02/May/14 |
|
| Status: | Resolved |
| Project: | OpenFlowPlugin |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | David Splittberger | Assignee: | Vaclav Demcak |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Linux |
||
| External issue ID: | 475 |
| Description |
|
Sending a delete message to the controller via REST to wildcard delete all the flows in a specific table does not result in a flow mod message being sent from the controller to the switch. I used tcpdump to cap packets leaving the controller with a source/destination port of 6653 to verify whether or not the flow mod was ever being sent. Steps to reproduce: 1. add flow to switch <?xml version="1.0" encoding="UTF-8" standalone="no"?> 2. verify flow was installed on switch ovs-ofctl --protocols OpenFlow13 dump-flows s1 3. send delete, specifying table only Actual results: ovs-ofctl --protocols OpenFlow13 dump-flows s1 Expected results: |
| Comments |
| Comment by David Splittberger [ 03/Mar/14 ] |
|
I get some output on the controller when I issue the table delete command: 2014-03-03 17:39:52.668 EST [http-bio-8080-exec-3] INFO o.o.c.sal.restconf.impl.BrokerFacade - Delete Configuration via Restconf: /(urn:opendaylight:inventory?revision=2013-08-19)nodes/(urn:opendaylight:inventory?revision=2013-08-19)node[ {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:5}]/(urn:opendaylight:flow:inventory?revision=2013-08-19)table[ {(urn:opendaylight:flow:inventory?revision=2013-08-19)id=0}] And if I try to delete individual flows via /restconf/config/opendaylight-inventory:nodes/node/openflow:5/table/0/flow/2 then the flow gets deleted fine. |
| Comment by Abhijit Kumbhare [ 14/Apr/14 ] |
|
New data store will solve this. Vaclav would be the contact for this. |
| Comment by Vaclav Demcak [ 02/May/14 ] |
|
New tree-based data store is made as default and I haven't seen described behavior anymore. |