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:

It seems that pulp isn't obeying the concurrency weight properly.  Too many syncs run given the set concurrency and weight.


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

How reproducible:
always 

Steps to Reproduce:
1.  Set concurrency_threshold to 5 in server.conf
2.  Set sync_weight to 2 in server.conf
3.  Restart httpd
4.  Initiate 4 syncs

Actual results:
Three of the syncs seem to run


Expected results:
Only 2 should run at any one time

I've been unable to reproduce this, but I didn't notice some behavior that seems confusing.

I followed the directions and started 4 syncs.
2 syncs kicked off immediately, and the other 2 waited.
The third sync started while the first was publishing.
This can give the impression that those two syncs are running concurrently, but the publish is actually a separate task from the sync in the dispatch system, even though they are grouped together (and their execution tracked together).

I'm going to close this bug. We can re-open if someone else is able to reproduce it.