Fix mistake in usage drop_constraint parameters

In migration e197124d4b9_add_unique_constrain mistake in usage
drop_constraint parameter type_ and positional arguments name
and table_name.

The same mistake was already fixed in migration
63afba73813_ovs_tunnelendpoints_id_unique.

Change-Id: I6a250e55ea53048bb11afd71fecf94da6f0c7421
Closes-bug: #1257607

diff --git a/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py b/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py
index 897c8aac2aa0b0a10c670bbe9a8ad7a6c0e5af5c..b2f4b5a8793cd83f24c443945edd32064c5a62df 100644 (file)
--- a/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py
+++ b/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py
@@ -59,7 +59,7 @@ def downgrade(active_plugins=None, options=None):
         return
 
     op.drop_constraint(
-        name=CONSTRAINT_NAME,
-        tablename=TABLE_NAME,
-        type='unique'
+        CONSTRAINT_NAME,
+        TABLE_NAME,
+        type_='unique'
     )