https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OPNFLWPLUG-189 OpenFlowPlugin <p>odl:<br/> version.properties <br/> org.opendaylight.controller.version = 0.1<br/> org.opendaylight.controller.build.scm.version = 2fffd8cdb3ed75f478b900c677bb4d97e5e91c9c<br/> org.opendaylight.controller.build.user = jenkins-controller<br/> org.opendaylight.controller.build.workspace = **********<br/> org.opendaylight.controller.build.timestamp = 1402444582255<br/> org.opendaylight.controller.build.machine = **********</p> <p>test: mininet 2.1.0 + ovs 2.0.0</p> <p>steps:<br/> 1) PUT xml /restconf/config/opendaylight-inventory:nodes/node/openflow:${switch_idx}/table/${table_id}/flow/${flow_id}<br/> (xml file f111.xml in attachment)</p> <p>2) GET its operational state (for full details see f111odb.xml in attachment)<br/> 3) GET its config</p> <p>4) seen difference<br/> config:<br/> &lt;out_group&gt;2&lt;/out_group&gt;<br/> oprational:<br/> not present</p> <p>Operating System: Linux<br/> Platform: PC</p> OPNFLWPLUG-189

of-flow: out_group missing in operational data store (but configured)

Bug Resolved Cannot Reproduce Anil Vishnoi Peter Gubka Wed, 11 Jun 2014 11:46:41 +0000 Mon, 27 Sep 2021 09:01:13 +0000 Fri, 13 Jun 2014 19:06:10 +0000 General 0 2 <p>Attachment f111.xml has been added with description: flow to be configured</p> <p>Attachment f111odb.xml has been added with description: operational details of the flow</p> <p>Hi Peter,</p> <p>This seems to similar to the case as i mentioned in <a href="https://jira.opendaylight.org/browse/OPNFLWPLUG-188" title="of-flow: instruction (push-vlan-action) different in config and operational db" class="issue-link" data-issue-key="OPNFLWPLUG-188"><del>OPNFLWPLUG-188</del></a>. I installed the flow (f111.xml) through restconf and i see following flow installed to the switch </p> <p>mininet&gt; sh ovs-ofctl dump-flows s1 -O OpenFlow13<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> 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</p> <p>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</p> <p>"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"</p> <p>Thanks<br/> Anil</p> Development External issue ID 1184 External issue URL Rank 0|i02zm7: