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.

If users deploy different #s of connected Content Hosts they have to reconfigure various settings for qpid to allow more than 225 and up:

https://access.redhat.com/solutions/1375253

We should reconfigure some of the values mentioned in that KCS during our installer puppet run to default to supporting at least 10K Content Hosts and possibly more.

What's expected behavior here? Something like: `--capsule-expected-hosts-count`?

Reset docs contact <> daobrien

VERIFIED

on sat6.2.0 snap19.1

I've set up a centos7 docker image with pre-installed subscription-manager and katello-consumer certificate from my satellite server.

I then ran many containers in a loop.

After triggering some batch package installation from WebUI, the number of qpid queues started to grow. I ended at 570 as that was as much containers i was able to start (didn't try to go further)
Seems like this amount of clients handled well

# qpid-stat -q --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 | grep -c pulp.agent
570

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