Operating System: All
Platform: All

These flows are configured successfully, but fail to be written on OVS.

Attachment flows_config_ds_table6.txt has been added with description: Flows configured in table6

To filter out redundand logging

log:set ERROR org.opendaylight.groupbasedpolicy

Attachment karaflog.txt has been added with description: karaf.log

Missing flows can be seen directly in CSIT job:

ODL data (including inventory/nodes config/operational) and flows on OVS switches can be seen directly in groupbasedpolicy CSIT job:
https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-3-node-only-boron/694/robot/report/log.html#s1-s2-s6

Please notice that flows for table6 are missing.
https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-3-node-only-boron/694/robot/report/log.html#s1-s2-s6-t1-k3-k2

Hi Tomas,

I guess you are seeing the flows in the inventory config DS , but not in the switch . Am i correct ?

if yes:

given this in the log :

2016-06-24 12:01:56,979 | ERROR | on-dispatcher-77 | DataTreeChangeListenerActor | 185 - org.opendaylight.controller.sal-distributed-datastore - 1.4.0.SNAPSHOT | Error notifying listener org.opendaylight.controller.md.sal.binding.impl.BindingClusteredDOMDataTreeChangeListenerAdapter@38b0d026
java.lang.NullPointerException: Match value must not be null
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:226)[65:com.google.guava:18.0.0]
at org.opendaylight.openflowplugin.impl.registry.flow.FlowRegistryKeyFactory$FlowRegistryKeyDto.<init>(FlowRegistryKeyFactory.java:43)[205:org.opendaylight.openflowplugin.impl:0.3.0.SNAPSHOT]
at org.opendaylight.openflowplugin.impl.registry.flow.FlowRegistryKeyFactory.create(FlowRegistryKeyFactory.java:29)[205:org.opendaylight.openflowplugin.impl:0.3.0.SNAPSHOT]
at org.opendaylight.openflowplugin.impl.services.SalFlowServiceImpl.addFlow(SalFlowServiceImpl.java:86)[205:org.opendaylight.openflowplugin.impl:0.3.0.SNAPSHOT]

It looks like having a non-null match s what is mandated by the inventory.

Can you please try with a non-null match and let us know if that works ?

Hi Shuva, so i tried to add empty match instead of null one and it helped.

Thanks for pointing that out.

Fixed in GBP
https://git.opendaylight.org/gerrit/#/c/40812/

cool ....

Reviewing the openflow specifications and post discussions, i feel having no match in the request is entirely fine, because data store doesn't put any restriction, and hence we should handle it internally.

The gerrit patch for the same is
https://git.opendaylight.org/gerrit/#/c/41605/ .

closing bug since the patch was merged already in boron and beryllium