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.
Descriptionsthirugn@redhat.com
2015-12-07 17:12:35 UTC
Description of problem:
client request timed out when trying to apply 300+ errata
Version-Release number of selected component (if applicable):
Sat 6.1.5 Compose 3
How reproducible:
Always
Steps to Reproduce:
1. Sync rhel 6 repo, create content view, publish, promote and attach it to activation key
2. Register a client using the above activation key, install katello agent, and run `katello-package-upload` in the client
3. Navigate to Satellite UI -> Content -> Errata -> Select 350+ errata and apply to the content host (Note: the errata are already available in content host's environment, so action is just apply errata and not incremental update)
4. Monitor satellite and the client logs
Actual results:
Client timed out.
* Satellite error: See attached `production.log error`
* Client error: /var/log/messages: see attached `client var log messages`
* Client yum history: Return-Code : ** Aborted **. More info in attached `client yum history`
Expected results:
Errata applied without error
Additional info:
Comment 6sthirugn@redhat.com
2015-12-07 18:49:30 UTC
*** This bug has been marked as a duplicate of bug 1277269 ***