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.

Busy Satellites generally benefit from adding a second dynflowd executor. 
A proper workaround is to change `/etc/sysconfig/dynflowd` like this:
~~~
  ...snip...
#Set the number of executors you want to run
#EXECUTORS_COUNT=1   <===== keep this line commented as it is
EXECUTORS_COUNT=2    <===== add this line please, uncommented
  ...snip...
~~~

custom-hiera.yaml should include this setting so that it can be persisted across Satellite updates and upgrades.

*** This bug has been marked as a duplicate of bug 1667405 ***