Red Hat Bugzilla – Bug 1394470
keystone does not retry on deadlock Transactions [500 Error]
Last modified: 2017-05-17 15:46:13 EDT
Created attachment 1219990 [details] keystone_exception.txt Description of problem: DBDeadlock: (pymysql.err.InternalError) (1213, u'Deadlock found when trying to get lock; try restarting transaction') The above error is retry-able error, but no evidence for keystone would really did a retry before throwing a 500. Version-Release number of selected component (if applicable): python-keystone.noarch 1:10.0.0-3.el7ost @rhos-10.0-puddle python-keystoneauth1.noarch 2.12.2-1.el7ost @rhos-10.0-puddle python-keystoneclient.noarch 1:3.5.0-1.el7ost @rhos-10.0-puddle python-keystonemiddleware.noarch 4.9.0-1.el7ost @rhos-10.0-puddle How reproducible: Unknown
How can I reproduce this?
Looks like it was fixed upstream. Changing the external bug to link to the older discussions
Should be fixed in all versions of OSP 11.
verified for openstack-keystone-11.0.0-0.20170127043446.cefbc3c.el7ost.noarch When using a MariaDB Galera cluster, the error happens due a race condition [1]. To try to reproduce the error, I've run a big concurrency rally scenario test that would create and delete several roles and projects - this triggers several revocation events. No error was reported or found in keystone logs. Marking as verified due the lack of evidence the issue persists rather than an actual validation. [1] http://lists.openstack.org/pipermail/openstack-dev/2015-February/056007.html
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1245