From 9467a6602ef31c1976b64539fdd4bfc4b63a2c95 Mon Sep 17 00:00:00 2001 From: Chris Yeoh Date: Fri, 22 Mar 2013 08:45:13 +1030 Subject: close db migration session Explicitly close sessions in db migration 022. With the postgresql backend if the session is not closed explicitly it leaves a user of the db behind which can cause problems later on Fixes bug #1158544 Change-Id: I389b83397addc5901aa94b584856fbd7f5cef485 --- .../common/sql/migrate_repo/versions/022_move_legacy_endpoint_id.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/keystone/common/sql/migrate_repo/versions/022_move_legacy_endpoint_id.py b/keystone/common/sql/migrate_repo/versions/022_move_legacy_endpoint_id.py index 7ccc1078..0c2db050 100644 --- a/keystone/common/sql/migrate_repo/versions/022_move_legacy_endpoint_id.py +++ b/keystone/common/sql/migrate_repo/versions/022_move_legacy_endpoint_id.py @@ -30,6 +30,7 @@ def upgrade(migrate_engine): endpoint_table.c.extra: json.dumps(extra), endpoint_table.c.legacy_endpoint_id: legacy_endpoint_id}) migrate_engine.execute(q) + session.close() def downgrade(migrate_engine): @@ -50,3 +51,4 @@ def downgrade(migrate_engine): endpoint_table.c.extra: json.dumps(extra), endpoint_table.c.legacy_endpoint_id: None}) migrate_engine.execute(q) + session.close() -- cgit