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
2017-08-18 20:06:18 UTC
Description of problem:
Bulk package profile update calls right after client registration causes failure of subsequent client registrations to Satellite.
Version-Release number of selected component (if applicable):
Satellite 6.2.11
How reproducible:
Always
Steps to Reproduce:
1. Register multiple clients (5 to 10) to Satellite6 concurrently - with each of them running puppet modules to pull content from Satellite6 right after registration
Actual results:
In the customer environment, there were 40 package profile updates per host right after client registration which slowed down Satellite and made subsequent client registrations to fail. Note that the subscription-manager on the client have a 60 sec default timeout which is not configurable at this time.
Expected results:
Reduce the package profile update processing time so cases like this (40 package profile updates per host right after registration) does not consume lot of Satellite resources and delay registration of subsequent clients.
Additional info:
Package profile processing logic needs to be improved to make it faster
- During the investigation, it was found that katello_installed_packages need to be indexed as this table might grow very quickly
- Need to de-duplicate the data in the table
Comment 4sthirugn@redhat.com
2017-09-15 17:43:08 UTC