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 registering more than ~240 in parallel getting this error "HTTP error (500 - Internal Server Error): Unable to register system, not all services available"

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

katello_version = katello-3.16.0-1.el7sat.noarch
satellite_version = satellite-6.8.0-1.el7sat.noarch


Steps to Reproduce:

- Try to run concurrent registration on Satellite 6.8

Actual results: 

~~~

"HTTP error (500 - Internal Server Error): Unable to register system, not all services available", "[\u001b[91mERROR\u001b[0m], [2020-09-24 19:47:16], EXITING: [/usr/sbin/subscription-manager register --org 'Default_Organization' --name 'satellite.example.compcontainer358.example1.local' --activationkey 'ActivationKey1'  --serverurl=https://satellite.example.com:443/rhsm --baseurl=https://satellite.example.com/pulp/repos --force] failed to execute properly."]}

~~~

Additional Info :

Checked the status of foreman-maintain service status -b and hammer ping commands.

The result - All OK (All services are running)

Hi Imaan! 

Can we have access to this system or get a foreman-debug from it?  (we're particularly interested in /var/log/httpd and /var/log/foreman

Thanks

After discussion it was determined that the Satellite was deployed with default tuning. Recommend re-running with appropriate --tuning parameter applied.

Hello

changing QA contact because Performance keyword present

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366