I use OpenVSwitch and occasionally upgrade from the tip of master. My previous upgrade was in Sep/2014, and I have just upgraded to last Friday's tip. A number of previously running test cases (using oftest) now fail for me, and I am investigating.
The v1.3 test basic.OutputExact creates a flow outputting to port 1, then sends packets in ports 2, 3 and 4. The flow is then changed to output to port 2 instead. Since everything else about the flow is the same, this actually represents a change in the same flow (in my opinion) and therefore the dpif flows created when packets were received should now be invalid. However, when a packet is sent on port 3, instead of being output to port 2, it is output to port 1, causing the test to fail. I think what's happening is that the dpif flows are not being deleted when the flow changes. I am almost certain that this is not how the code used to behave. I have also tweaked the test to explicitly remove the flow before changing the output port, and this test passes. The questions I have are: Can anyone point me to the code change that might have introduced this behaviour? Is it a deliberate change or a by-product? While I could happily proceed by changing our regression test, I would rather see if this behaviour can be altered to behave the way it used to, which seems to me to be more conformant to the specification. Any advice gratefully accepted. Tony
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
