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.

Verified in Satellite 6.3.1 Snap 2.

I ran content-host-d's flood script to register 5000 new content hosts within 1h 25m. During the process, there were always 50 concurrent registrations. At no point did any of the hosts encounter the "host_id has already been taken" error.

The only two registrations that failed were due to this unrelated error:
"Unable to register system, not all services available"
Which is likely due to the Satellite struggling under the registration load.
The failed systems were bad1835 and bad3606.

I am attaching the logs for the script as well as all of the registered clients.

# python flood.py -s ibm-x3550m3-10.lab.eng.brq.redhat.com -t rhel72 -c 5000 -n bad --limit 50 --exit-criteria regis

project source: https://github.com/JacobCallahan/content-host-d

Created attachment 1417261 [details]
script logs

Created attachment 1417262 [details]
client logs

this was released in 6.3.1.