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 - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Vladimír Sedmík <vsedmik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: aruzicka, inecas
Target Milestone: UnspecifiedKeywords: FutureFeature
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: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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: