Bug 1956261

Summary:	[RFE] Avoid the possibilty of mistakenously trigger the same capsule sync more than once in parallel
Product:	Red Hat Satellite	Reporter:	Francesco Ratto <fratto>
Component:	Capsule - Content	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	ahumbe, aruzicka, dalley, inecas, thadzhie
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-30 03:30:45 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 Francesco Ratto 2021-05-03 10:33:29 UTC

Description of problem:During normal use of capsule server it is possible to mistakenly trigger more than a single sync in parallel on the same capsule server.This is causing slowness and disruption to the satellite and capsule server 


Version-Release number of selected component (if applicable):


How reproducible: always 


Steps to Reproduce:
1.start 2 capsule sync on the same capsule server 
2.
3.

Actual results:the two (or more syncs) overlap causing slowness and ultimately disruption 


Expected results: It should not be possible to trigger two or more syncs on the same server in parallel . Is it clear this is an operational mistake but a lock could easily avoid such a mistake 


Additional info:

Comment 1 Daniel Alley 2022-08-30 03:30:45 UTC

If they actually _overlap_ then this is definitely a bug in the Pulp 2 tasking system (as opposed to an RFE - this already shouldn't happen).  However being Pulp 2 I wouldn't be surprised.

We've torture tested the Pulp 3 tasking system to a much greater extent and it has been vastly more reliable overall. I think we can safely close this without more recent reports of issues.

Comment 2 Daniel Alley 2022-08-30 03:32:23 UTC

Also there is more discussion on https://bugzilla.redhat.com/show_bug.cgi?id=1581415 which seems to be very similar

Comment 3 Daniel Alley 2022-08-30 03:35:18 UTC


*** This bug has been marked as a duplicate of bug 1581415 ***