Kyle Mestery e177954b56 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

..

__init__.py

Rename Quantum to Neutron

2013-07-06 15:02:43 -04:00

test_agent_scheduler.py

Utilizes assertIsNone and assertIsNotNone

2013-10-03 23:01:48 +00:00

test_openvswitch_plugin.py

Openvswitch update_port should return updated port info

2014-02-28 12:44:36 -06:00

test_ovs_db.py

replace rest of q_exc to n_exc in code base

2014-03-03 17:42:20 -08:00

test_ovs_defaults.py

Rename Quantum to Neutron

2013-07-06 15:02:43 -04:00

test_ovs_lib.py

Don't set priority when calling mod_flow

2014-03-21 09:44:34 +00:00

test_ovs_neutron_agent.py

Don't set priority when calling mod_flow

2014-03-21 09:44:34 +00:00

test_ovs_rpcapi.py

Replace stubout with fixtures

2013-11-24 10:46:08 -05:00

test_ovs_security_group.py

Removes calls to mock.patch.stopall in unit tests

2014-03-12 04:17:11 +00:00

test_ovs_tunnel.py

Don't set priority when calling mod_flow

2014-03-21 09:44:34 +00:00