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