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: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:

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.

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

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