Adit Sarfaty 70fbe736b7 NSX-V3: Fix QoS delete ... In commit I1f863bf91f712d4b12db753b13cc6b842b6918a4 the qos driver stopped using the message queue. So the delete callback is now called in the plugin context, after the qos policy is already deleted. This means that we cannot access the backend profile id in the DB, since it was already deleted too. The fix is to remove the foreign key constraint from the mapping table, and manually delete the entry. Change-Id: I28e1c7c5ad0bb487d9c19ce76e2f7820f029678e		2017-03-15 13:58:27 +02:00
..
liberty	Tag the alembic migration revisions for Mitaka	2016-03-20 08:10:04 +00:00
mitaka/expand	Ensure migrate script pass on newer MySQL	2016-05-25 16:58:12 +08:00
newton	Fix ipam table primary key constraint	2017-02-16 08:45:55 +02:00
ocata	NSX|V: move migration to correct folder	2017-02-27 14:52:54 +00:00
pike	NSX-V3: Fix QoS delete	2017-03-15 13:58:27 +02:00
CONTRACT_HEAD	NSX-V3: Fix QoS delete	2017-03-15 13:58:27 +02:00
EXPAND_HEAD	Fix LBAAS L7 policy upgrade	2017-02-27 08:03:05 +02:00
kilo_release.py	Move vmware_nsx/neutron/db to vmware_nsx/db	2015-09-14 16:45:18 -07:00