[OPNFLWPLUG-189] of-flow: out_group missing in operational data store (but configured) Created: 11/Jun/14  Updated: 27/Sep/21  Resolved: 13/Jun/14

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

Type: Bug
Reporter: Peter Gubka Assignee: Anil Vishnoi
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

Attachments: File f111.xml     File f111odb.xml    
External issue ID: 1184

 Description   

odl:
version.properties
org.opendaylight.controller.version = 0.1
org.opendaylight.controller.build.scm.version = 2fffd8cdb3ed75f478b900c677bb4d97e5e91c9c
org.opendaylight.controller.build.user = jenkins-controller
org.opendaylight.controller.build.workspace = **********
org.opendaylight.controller.build.timestamp = 1402444582255
org.opendaylight.controller.build.machine = **********

test: mininet 2.1.0 + ovs 2.0.0

steps:
1) PUT xml /restconf/config/opendaylight-inventory:nodes/node/openflow:${switch_idx}/table/${table_id}/flow/${flow_id}
(xml file f111.xml in attachment)

2) GET its operational state (for full details see f111odb.xml in attachment)
3) GET its config

4) seen difference
config:
<out_group>2</out_group>
oprational:
not present

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

Attachment f111.xml has been added with description: flow to be configured

Comment by Peter Gubka [ 11/Jun/14 ]

Attachment f111odb.xml has been added with description: operational details of the flow

Comment by Anil Vishnoi [ 13/Jun/14 ]

Hi Peter,

This seems to similar to the case as i mentioned in OPNFLWPLUG-188. I installed the flow (f111.xml) through restconf and i see following flow installed to the switch

mininet> sh ovs-ofctl dump-flows s1 -O OpenFlow13
OFPST_FLOW reply (OF1.3) (xid=0x2):
cookie=0xa, duration=16.946s, table=2, n_packets=0, n_bytes=0, idle_timeout=34, hard_timeout=60, priority=111,ip,nw_dst=10.0.0.0/24 actions=strip_vlan

So there is not out_group element exist in the installed flow. I think possible reason behind OVS ignoring this flow is as follows as per spec

"The out_port and out_group fields optionally filter the scope of OFPFC_DELETE and OFPFC_DELETE_STRICT messages by output port and group. If either out_port or out_group contains a value other than OFPP_ANY or OFPG_ANY respectively, it introduces a constraint when matching. This constraint is that the flow entry must contain an output action directed at that port or group. Other constraints such as ofp_match structs and priorities are still used; this is purely an additional constraint. Note that to disable output filtering, both out_port and out_group must be set to OFPP_ANY and OFPG_ANY respectively. These fields are ignored by OFPFC_ADD, OFPFC_MODIFY or OFPFC_MODIFY_STRICT messages"

Thanks
Anil

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