InvalidInput errors in the unittests

[Lucas Alvares Gomes]

When running the unittests we can see a couple of InvalidInput errors being raised in some of the tests, it doesn't seem to affect the result of the run (since it does end successfully) but it's probably something we want to get fixed to avoid confusion.

An example of these errors is:

networking_ovn.tests.unit.test_ovn_parent_tag.TestOVNParentTagPortBinding.test_create_port_with_parent_and_tag [1.655266s] ... ok
Mechanism driver 'ovn' failed in create_port_precommit
Traceback (most recent call last):
  File "/home/lucas/Projects/networking-ovn/.tox/py27/src/neutron/neutron/plugins/ml2/managers.py", line 428, in _call_on_drivers
    getattr(driver.obj, method_name)(context)
  File "networking_ovn/ml2/mech_driver.py", line 359, in create_port_precommit
    utils.validate_and_get_data_from_binding_profile(port)
  File "networking_ovn/common/utils.py", line 145, in validate_and_get_data_from_binding_profile
    raise n_exc.InvalidInput(error_message=msg)
InvalidInput: Invalid input for operation: Invalid binding:profile. ['vtep-physical-switch', 'vtep-logical-switch'] are all required..

See more at: http://paste.openstack.org/show/624436/

---

To reproduce it, simply run the unittests as:

$ tox -epy27