Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When publishing a content view, encountering a deadlock

Version-Release number of selected component (if applicable):
python39-pulpcore-3.21.18-1.el8pc.noarch
satellite-6.13.5-1.el8sat.noarch

How reproducible:
Not reproducible

Steps to Reproduce:
1.
2.
3.

Actual results:
""class"":""Dynflow::ExecutionPlan::Steps::Error"",""exception_class"":""ActiveRecord::Deadlocked"",""message"":""PG::TRDeadlockDetected: ERROR:  deadlock detected\nDETAIL:  Process 3250880 waits for ShareLock on transaction 62043418; blocked by process 3271050.\nProcess 3271050 waits for ShareLock on transaction 62043419; blocked by process 3250880.\nHINT:  See server log for query details.\nCONTEXT:  while inserting index tuple (472,1) in relation \""katello_errata\""\n""}",,

Expected results:
No deadlock

Additional info:

The place to start would be checking if other tasks like imports/exports/syncs/etc were running at the same time as the content view publish. https://bugzilla.redhat.com/show_bug.cgi?id=1957144 might be related.

(In reply to Ian Ballou from comment #3)
> The place to start would be checking if other tasks like
> imports/exports/syncs/etc were running at the same time as the content view
> publish. https://bugzilla.redhat.com/show_bug.cgi?id=1957144 might be
> related.

Since their were scripts that initiated syncs and exports during the publish, and the issue is not reproducible, we will assume this was a matter of coincidence and close this Bugzilla. Thanks.