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:
Per bug #745652 and bug #749495, katello installer configures # of thin processes based on cpu and memory constraints of the system. This is an initial configuration; presumably, if a user upgrades the host system at some point, katello will not be optimally configured to take advantage of the new system specs.
That said, I'm not sure how easy or difficult it will or should be for system admins to update the katello config files accordingly.
We should have a kbase article outlining how to manually increase allowed thin processes to accommodate new hardware. Alternately, this could be part of a larger tuning guide.
Cloned for the doc request for a CFSE Tuning Guide.
Assigned this original bug to Bryan Kearney, to re-assign as he sees fit to someone who can write the kbase article.
LKB