[OPNFLWPLUG-273] of-flow: different tags in config and operational (set-nw-dst-action) Created: 12/Sep/14  Updated: 27/Sep/21  Resolved: 18/Sep/14

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

Type: Bug
Reporter: Peter Gubka Assignee: Martin Bobak
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC

External issue ID: 1840

 Description   

odl:
cat version.properties
org.opendaylight.controller.version = 0.1
org.opendaylight.controller.build.scm.version = 41f7153fe534ac2dee4137eff6e3523f576504e3
org.opendaylight.controller.build.user = jenkins-controller
org.opendaylight.controller.build.workspace = **********
org.opendaylight.controller.build.timestamp = 1410495075324
org.opendaylight.controller.build.machine = **********

adding the flow from
integration.git test/csit/variables/xmls/f34.xml

has action
<action>
<order>0</order>
<set-nw-dst-action>
<ipv4-address>10.0.0.21/24</ipv4-address>
</set-nw-dst-action>
</action>

on the switch it looks like:
cookie=0xa, duration=24.973s, table=2, n_packets=0, n_bytes=0, idle_timeout=300, hard_timeout=600, send_flow_rem priority=34,ip,nw_dst=10.0.0.0/24 actions=set_field:10.0.0.21->ip_dst

in operational ds:
<action>
<order>0</order>
<set-field>
<ipv4-destination>10.0.0.21/32</ipv4-destination>
</set-field>
</action>

is that behavior correct ?

 Comments   
Comment by Martin Bobak [ 17/Sep/14 ]

This behavior is correct. OF 1.3. uses set_field action, which was not present in OF 1.0. If OF 1.0 action set-nw-dst-action is called, it is stored as OF 1.3. We do OF 1.0 -> OF 1.3. translation, but not opposite direction.

Comment by Abhijit Kumbhare [ 18/Sep/14 ]

As Martin said OF 1.0 -> 1.3 backward compatibility is present but OF 1.3 -> 1.0 forward compatibility is a non-goal.

Comment by Michal Rehak [ 18/Sep/14 ]

Peter, you can use set-field element in order to get closer match between DS/operational and DS/config. But there is increasing number of flows where we need to put something different than it was pushed to DS/config. Probably we would need at least a pair of xmls for each test (DS/config input and DS/operational compare data).

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