x
/
group-based-policy
Code Issues Proposed changes

Fix DB migration on AIM data 

Starting revision cc09261e0fb5, alembic migration transactions
seem to break to the point that the gbp_alembic_version value
in the database after a successful migration end up being 1 or 2
versions behind. The root cause seems to be a missing commit
during the AIM data migration that this patch is adding back.

Change-Id: I22e58454c4294cd502d019cb81ab0c1c176b77f1
This commit is contained in:
Ivar Lazzaro 2017-09-29 14:31:43 -07:00
parent a095707c01
commit 8d5f92c277
No known key found for this signature in database
GPG Key ID: ACEEC8CB558DC3CF
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
gbpservice/neutron/db/migration/alembic_migrations/versions/cc09261e0fb5_apic_aim_persist.py
View File

@ -69,7 +69,7 @@ def upgrade():
from gbpservice.neutron.plugins.ml2plus.drivers.apic_aim import (
data_migrations)
session = sa.orm.Session(bind=bind)
session = sa.orm.Session(bind=bind, autocommit=True)
data_migrations.do_apic_aim_persist_migration(session)
except ImportError:
util.warn("AIM schema present, but failed to import AIM libraries"