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:
This bug is a tracker for using the new bulk repo query API in pulp (mark this MODIFIED when katello supports this api).  For more details see the dependent bug

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Dep ON_QA. Please reopen when necessary.

Katello still creating repos one at a time, slows to a crawl for at least 15 minutes.  During that time all pages take way too long to load (like 3 minutes).

katello-0.1.135-1.git.0.668aa1d.el6.x86_64

I believe this bug is only fixed when katello uses the new pulp API that does batch operations.

Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Taking.
I belive this fix is addressed in current upstream and will be fixed in next version of CFSE, where we will be rebasing on current upstream.

moving to 2.0 since we didn't really make any inherent performance fixes for imports during 1.1

These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.