From time to time, I see the following error in our nightly pipelines: <pre> not ok 1 Delete an Organization # (in test file fb-destroy-organization.bats, line 15) # `hammer organization delete --name="${ORGANIZATION}"' failed with status 70 # Task fdb90a4d-89fc-4509-9bee-b87f7fbb5e89 planned: 0.0/1, 0%, elapsed: 00:00:00 # Task fdb90a4d-89fc-4509-9bee-b87f7fbb5e89 running: 0.021739130434782608/1, 2%, 0.0/s, elapsed: 00:00:02, ETA: 00:01:55 # Task fdb90a4d-89fc-4509-9bee-b87f7fbb5e89 running: 0.16304347826086957/1, 16%, 0.0/s, elapsed: 00:00:05, ETA: 00:00:28 # Task fdb90a4d-89fc-4509-9bee-b87f7fbb5e89 running: 0.2391304347826087/1, 23%, 0.0/s, elapsed: 00:00:07, ETA: 00:00:25 # Task fdb90a4d-89fc-4509-9bee-b87f7fbb5e89 running: 0.32608695652173914/1, 32%, 0.0/s, elapsed: 00:00:09, ETA: 00:00:20 # Task fdb90a4d-89fc-4509-9bee-b87f7fbb5e89 running: 0.4782608695652174/1, 47%, 0.0/s, elapsed: 00:00:12, ETA: 00:00:12 # Task fdb90a4d-89fc-4509-9bee-b87f7fbb5e89 running: 0.6739130434782609/1, 67%, 0.0/s, elapsed: 00:00:14, ETA: 00:00:06 # Task fdb90a4d-89fc-4509-9bee-b87f7fbb5e89 error: 0.75/1, 75%, 0.1/s, elapsed: 00:00:16, ETA: 00:00:04 # Task fdb90a4d-89fc-4509-9bee-b87f7fbb5e89 error: 0.75/1, 75%, 0.1/s, elapsed: 00:00:16, ETA: 00:00:04 # Error: PG::TRDeadlockDetected: ERROR: deadlock detected # DETAIL: Process 20568 waits for ShareLock on transaction 18434; blocked by process 23406. # Process 23406 waits for ShareLock on transaction 18406; blocked by process 20568. # HINT: See server log for query details. # : DELETE FROM "katello_pool_products" WHERE "katello_pool_products"."id" = $1 </pre>
Created from redmine issue https://projects.theforeman.org/issues/26821
Upstream bug assigned to jsherril
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26821 has been resolved.
Verified on Satellite 6.6 snap 17. Trying to reproduce bug by deleting multiple organizations. Everything works fine, no error occurred in logs.
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/RHSA-2019:3172