Updated openstack/openstack
Project: openstack/keystone  1f6cce7525b04a4ba7b2fe26a999651fadc15473
null
One transaction per call to sql assignment backend

There are numerous schedules that lead to inconsistent data in the
various grant tables and role table. These races arose from a lack of
synchronization during grant table modification (i.e., during grant
record creation + deletion and role deletion) and deletions of records
that grant records refer to (i.e., user, group, domain, and project
records). The races manifested as 404 errors in response to API
requests. This patch adds the necessary synchronization by way of
transactions.

Also removed pointless session.flush() calls at the ends of transactions.

Closes-Bug: #1246489
Change-Id: I958d48bafc7fcb95f1d9ea71e408b4cefc2469c9
Updated openstack/openstack
Project: openstack/swift  47c65386dd83df16a127140dd42ad14f8e5cc418
null
Fixed DB test cases on PyPy

They weren't working because of the intersection between some monkey
patching in the tests and the fact that ``sqlite3.Connection`` and
``Cursor`` are Python classes on PyPy, but C-extension classes on
CPython. The result was that trying to call the superclass's init
didn't work because the name ``sqlite3.Connection`` pointed to a
different class that wasn't actually the real superclass of
``GreenDBConnection``. Using ``super`` fixes this because the method
called is now always the real superclass's.

Change-Id: Ib45b16c7499883e560877788f13285d0a47cc2cd