We've discovered we can deadlock on allocations, and reviewing
the code of both the test and the underlying db, it is sort of a
"multiple things contribute scenario", but first up here is to
streamline the allocations update process so we re-query after
closing out the transaction.
Change-Id: I46e78813787703819a61f69d4243271ec07e0983
Partial-Bug: #2028866
(cherry picked from commit cc9af373e7120bdf7699c370e118d5f11171b573)
Reviewed: https:/ /review. opendev. org/c/openstack /ironic/ +/895038 /opendev. org/openstack/ ironic/ commit/ b35a9c78c6a5f11 63df10738f79922 9144282e30
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2023.1
commit b35a9c78c6a5f11 63df10738f79922 9144282e30
Author: Julia Kreger <email address hidden>
Date: Thu Jul 27 09:33:03 2023 -0700
DB: Streamline allocation interactions
We've discovered we can deadlock on allocations, and reviewing
the code of both the test and the underlying db, it is sort of a
"multiple things contribute scenario", but first up here is to
streamline the allocations update process so we re-query after
closing out the transaction.
Change-Id: I46e78813787703 819a61f69d42432 71ec07e0983 f7699c370e118d5 f11171b573)
Partial-Bug: #2028866
(cherry picked from commit cc9af373e7120bd