Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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: When scheduled lots of tasks in async, we occasionally get into "unresponsiveness" issue. To avoid/workaround this, we can not do async things and just wait for the tasks and do things one by one.
How reproducible: nondeterministic
Steps to Reproduce:
1. import multiple larger Red Hat repos
Actual results:
machine stops responding
Expected results:
...
Comment 1RHEL Program Management
2014-08-14 14:03:05 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
DEVELOPER VERIFIED:
1) start with a Sat6 that has its orgs and manifests, which has not sync'd any Red Hat content yet, and a channels.csv that has multiple Red Hat channels.
2) hammer import repository-enable --synchronize --wait
3) In the UI, go to <sat6>/katello/sync_management and Expand All
4) Note that *all* the repositories have sync-tasks started
Next:
1) start with a Sat6 that has its orgs and manifests, which has not sync'd any Red Hat content yet, and a channels.csv that has multiple Red Hat channels.
2) hammer import repository-enable --synchronize --wait --no-async
3) In the UI, go to <sat6>/katello/sync_management and Expand All
4) Note that at any given moment, only one repository is synchronizing, and that a new one starts when the first finishes.
Verified on rubygem-hammer_cli_import-0.10.4-1.1.el6sat.noarch