Hi guys, Following up on Yi Yan's message (I don't think I'll be able to attach this mail to the thread correctly since I wasn't subscribed to the list)
https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-July/005451.html I've confirmed that this issue is introduced because of some change in Openflowplugin project in the last ~3 weeks. What I did: reproduced the error (compiling latest version for SFC + snapshot version from openflowplugin). Then, I cloned openflowplugin repo, then checked out a version from ~3 weeks ago ( hash 1061cc9d6929e8bb2052f4562bedd7fdce5034ac; chosed that version for no particular reason, only that I commited a bugfix on SFC on that date and I checked the same chain config I'm rendering now was working then). Compiled openflowplugin version, then rebuild SFC on top of it, and the flows are rendered successfully (i.e. the "Match value must not be null" error disappears). So it must be some change in the openflowplugin since Jun 12th and now what is causing this error. Had a look at the openflowplugin changes since that date, but there has been a lot of merge activity and I saw nothing that is evident to me which could trigger this. In case it helps, on this test of mine (latest SFC, OpenflowPlugin from Jun 12th), flows in the config datastore do not contain any match rule, yet they're written successfully to the ovs switch. E.g: <flow><id>107</id><cookie_mask>20</cookie_mask><table_id>2</table_id><priority>5</priority><strict>false</strict><flags/><flow-name>MatchAny</flow-name><idle-timeout>0</idle-timeout><hard-timeout>0</hard-timeout><cookie>20</cookie><barrier>false</barrier><instructions><instruction><order>0</order><go-to-table><table_id>3</table_id></go-to-table></instruction></instructions></flow> BR, Diego
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
