{"push_id":1777532190,"size":1,"distinct_size":1,"ref":"refs/heads/stable/mitaka","head":"390118c5c6630a58b00b41b7a2e619b320bc26ee","before":"7e4345d5f4fa21c35949e52b9a8214a60d879e6b","commits":[{"sha":"390118c5c6630a58b00b41b7a2e619b320bc26ee","author":{"name":"Sumit Naiksatam","email":"0abfae75886b3901418ac06195e9dbe03539bf4b@gmail.com"},"message":"[apci_aim] Remove use of with_lockmode in ml2plus\n\nIn certain cases of concurrent operations we are seeing an error\nwhich suggests that a rolled back transaction is be reused. On debugging\nit has been observed that the error manifests when the code path\nexecutes the queries that are using with_lockmode in a couple of\nplaces in the ml2 plugin component. Removing the with_lockmode usage\nseems to prevent this issue and does not seem to be affecting the\ncorrectness of behavior even in concurrent execution situations.\n\nThis patch removes the use of the with_lockmode in the identified place\nwhen the ml2plus plugin configured.\n\nChange-Id: If65c238cbf49a9cfd2546ca26d37ee721f6f986c\n(cherry picked from commit 9d16f2cfa34822c3fb0ffc93d33ff4cc3f016352)","distinct":true,"url":"https://api.github.com/repos/openstack/group-based-policy/commits/390118c5c6630a58b00b41b7a2e619b320bc26ee"}]}
{"actor":{"display_login":"openstack-gerrit"}}