Bug 1956261 - [RFE] Avoid the possibilty of mistakenously trigger the same capsule sync more than once in parallel
Summary: [RFE] Avoid the possibilty of mistakenously trigger the same capsule sync mor...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.8.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-03 10:33 UTC by Francesco Ratto
Modified: 2021-05-17 11:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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:
Note You need to log in before you can comment on or make changes to this bug.