Bug 2252297

Summary:	Deadlock seen when publishing a content view
Product:	Red Hat Satellite	Reporter:	Taft Sanders <tasander>
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.13.5	CC:	dalley, iballou, rlavi
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-12-19 13:26:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Taft Sanders 2023-11-30 18:06:53 UTC

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:

Comment 3 Ian Ballou 2023-12-13 21:43:02 UTC

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.

Comment 5 Taft Sanders 2023-12-19 13:26:04 UTC

(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.