Kyle Mestery 252a83890a Don't set priority when calling mod_flow ... This commit [1] changed the behavior of modifying flows to not allow priority to be set on flow modification. The agent code which was calling mod_flow was not updated to respect this behavior. The unit tests were also not updated in this regard. I've corrected this behavior now, and added a negative UT case to catch this in the future. [1] https://review.openstack.org/#/c/58533/ Closes-Bug: #1295703 Change-Id: I20737637cc84567a5ec19efaad18e7f334007f18		2014-03-21 09:44:34 +00:00
..
etc	Service Type Framework refactoring	2013-07-25 21:47:30 +04:00
functional	Add configurable ovsdb monitor respawn interval	2013-11-20 15:16:27 -06:00
unit	Don't set priority when calling mod_flow	2014-03-21 09:44:34 +00:00
var	Rename Quantum to Neutron	2013-07-06 15:02:43 -04:00
__init__.py	Rename Quantum to Neutron	2013-07-06 15:02:43 -04:00
base.py	Merge "Fix misleading error message about failed dhcp notifications"	2014-03-21 05:10:41 +00:00
post_mortem_debug.py	Add post-mortem debug option for tests	2013-12-10 03:56:50 +00:00
tools.py	Replace mox in unit tests with mock	2013-11-18 22:17:14 +09:00