This is likely unfixable with the current state of affairs. we will need
to deal with conflicts etc as the arise in code.
** Changed in: keystone
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1282229
Title:
Race Conditions in SQLAlchemy Select, Update, Flush Transactions
Status in OpenStack Identity (keystone):
Won't Fix
Bug description:
In cases where Keystone does a SQL query, update a field (or set of
fields) on the model object, flush/update/commit the transaction,
there is potentially a race condition. Since an explicit
.with_lockmode('update') is not called, it is possible for a second
(think apache WSGI) keystone process to also perform an update on the
same row (or set of rows) causing the potential for loss of data.
This mostly presents in the case of the 'Extra' fields on the SQL
models, but potentially could affect a broader base (all SQL drivers
need to be evaluated).
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1282229/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
