[OPNFLWPLUG-182] flow in operational data store does not contain all details from cofig (e.g. <instructions>) Created: 06/Jun/14  Updated: 27/Sep/21  Resolved: 24/Jun/14

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Peter Gubka Assignee: Vaclav Demcak
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC

Attachments: File f2.xml    
External issue ID: 1149

 Description   

used odl:
org.opendaylight.controller.version = 0.1
org.opendaylight.controller.build.scm.version = 03eb0149e2d6e045e40d7cdf338ee060bc39f070
org.opendaylight.controller.build.user = jenkins-controller
org.opendaylight.controller.build.workspace = **********
org.opendaylight.controller.build.timestamp = 1401981249321
org.opendaylight.controller.build.machine = **********

mininet 2.1.0 with ovs 2.0.0

1) PUT flow (xml attached)
/restconf/config/opendaylight-inventory:nodes/node/openflow:${switch_idx}/table/${table_id}/flow/${flow_id}, data=${data}, headers=${headers}

2) GET config
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<flow xmlns="urn:opendaylight:flow:inventory">
<strict>false</strict>
<id>125</id>
<idle-timeout>34</idle-timeout>
<cookie_mask>255</cookie_mask>
<priority>2</priority>
<hard-timeout>60</hard-timeout>
<table_id>2</table_id>
<instructions>
<instruction>
<order>0</order>
<apply-actions>
<action>
<drop-action/>
<order>0</order>
</action>
</apply-actions>
</instruction>
</instructions>
<flow-name>FooXf2</flow-name>
<match>
<ethernet-match>
<ethernet-type>
<type>2048</type>
</ethernet-type>
</ethernet-match>
<ipv4-source>10.0.0.1</ipv4-source>
</match>
<cookie>2</cookie>
<installHw>false</installHw>
<barrier>false</barrier>
<flags>FlowModFlags [_cHECKOVERLAP=false, _rESETCOUNTS=false, _nOPKTCOUNTS=false, _nOBYTCOUNTS=false, _sENDFLOWREM=false]</flags>
</flow>

3) Get operational
<flow>
<id>125</id>
<flow-statistics xmlns="urn:opendaylight:flow:statistics">
<idle-timeout>34</idle-timeout>
<flags/>
<hard-timeout>60</hard-timeout>
<cookie>2</cookie>
<byte-count>0</byte-count>
<match>
<ipv4-source>10.0.0.1/32</ipv4-source>
<ethernet-match>
<ethernet-type>
<type>2048</type>
</ethernet-type>
</ethernet-match>
</match>
<duration>
<nanosecond>333000000</nanosecond>
<second>19</second>
</duration>
<priority>2</priority>
<packet-count>0</packet-count>
<table_id>2</table_id>
</flow-statistics>
</flow>

this bug can be related to https://bugs.opendaylight.org/show_bug.cgi?id=521

 Comments   
Comment by Peter Gubka [ 06/Jun/14 ]

Attachment f2.xml has been added with description: xml used to configure flow

Comment by Vaclav Demcak [ 24/Jun/14 ]

The provided xml input and the next xml imput have same device flow

{cookie=0x2, duration=23.331s, table=2, n_packets=0, n_bytes=0, priority=2,ip,nw_src=10.0.0.1 actions=drop}

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<flow xmlns="urn:opendaylight:flow:inventory">
<strict>false</strict>
<id>125</id>
<idle-timeout>34</idle-timeout>
<cookie_mask>255</cookie_mask>
<priority>2</priority>
<hard-timeout>60</hard-timeout>
<table_id>2</table_id>
<flow-name>FooXf2</flow-name>
<match>
<ethernet-match>
<ethernet-type>
<type>2048</type>
</ethernet-type>
</ethernet-match>
<ipv4-source>10.0.0.1</ipv4-source>
</match>
<cookie>2</cookie>
<installHw>false</installHw>
<barrier>false</barrier>
<flags>FlowModFlags [_cHECKOVERLAP=false, _rESETCOUNTS=false, _nOPKTCOUNTS=false, _nOBYTCOUNTS=false, _sENDFLOWREM=false]</flags>
</flow>

The spec says an empty action list means to drop the packet.

In another mindless theoretical sample :

<instructions>
<instruction>
<apply-actions>
<action>
<dec-mpls-ttl/>
<order>0</order>
</action>
<action>
<drop-action/>
<order>1</order>
</action>
</apply-actions>
<order>0</order>
</instruction>
</instructions>

The drop-action doesn't send to device. It is absolutely ignored.

So, drop-action has to be ignored in action's test check.

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