Red Hat Bugzilla – Bug 1242264
Default configurations should support higher than 225 Content hosts
Last modified: 2016-07-27 07:24:53 EDT
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