During a backport patch [0] for this fix
it was found some problems in the previous
approach like, It didn't enabled back the
session.autocommit. Another comment was we should
create a new session and commit on it instead of
disable/enable autocommit.
After this, we should backport this change in order
to fix the previous releases, instead of the other
one.
Reviewed: https:/ /review. openstack. org/482606 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=058ea426245 9be90f0721891b6 ac2d29600e77c1
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit 058ea4262459be9 0f0721891b6ac2d 29600e77c1
Author: Raildo Mascena <email address hidden>
Date: Tue Jul 4 14:10:16 2017 -0300
Fixing flushing tokens workflow
During a backport patch [0] for this fix autocommit. Another comment was we should
it was found some problems in the previous
approach like, It didn't enabled back the
session.
create a new session and commit on it instead of
disable/enable autocommit.
After this, we should backport this change in order
to fix the previous releases, instead of the other
one.
[0] https:/ /review. openstack. org/#/c/ 469514
Change-Id: Ifc024ba0e86bb7 1f4ab8b01991778 2bc5bf3be7a 61ec06b4e2465c8 d88b8c1725)
Closes-Bug: #1649616
(cherry picked from commit 0b5c5c03ecb6cd2