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.

This task takes 10 minutes approximately on decent sized server (which is in compliance with our minimum requirements - eight cores AMD Opteron 2358 SE with 32GB RAM).

This then blocks all incoming requests in Foreman and Puppet Master (which uses node.rb). One Passenger worker is completely blocked. It is pretty easy to consume all five workers (default Satellite 6.2 sizing) and then ALL requests gets enqueued, client time outs.

I hit this during client testing of 6.2 GA.

https://github.com/Katello/katello/commit/cd113485cc3b5b7a7cf59aa61d6c6660264d161a

Justin, what was reason for that? Kinda ruins my client tests :-)

Connecting redmine issue http://projects.theforeman.org/issues/12749 from this bug

Upstream bug component is Candlepin

Moving to POST since upstream bug http://projects.theforeman.org/issues/12749 has been closed

tested on snap 19.1

change looks good, I tested and did not see registrations blocking on profile update.

how I tested:

 * registered host to satellite (no-break test)
 * confirmed profile update did not finish before registration in CLI finished

as an additional test, I added a 10 second sleep to the pulp applicability call, and the registration still finished quickly.

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, 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/RHBA-2016:1501