Bug 1042529
| Summary: | Change qpid puppet module default for max_connections to be UINT16_MAX | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Perry Myers <pmyers> | |
| Component: | openstack-packstack | Assignee: | Ivan Chavero <ichavero> | |
| Status: | CLOSED ERRATA | QA Contact: | Attila Darazs <adarazs> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.0 | CC: | ajeain, aortega, derekh, dprince, ichavero, mmagr, oblaut, sclewis, sputhenp, yeylon | |
| Target Milestone: | z2 | Keywords: | TestOnly, ZStream | |
| Target Release: | 4.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-packstack-2013.2.1-0.21.dev948.el6ost | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1051601 (view as bug list) | Environment: | ||
| Last Closed: | 2014-03-04 19:13:05 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1024651, 1051601 | |||
|
Description
Perry Myers
2013-12-13 00:11:35 UTC
Changed the value of max_connections in the qpid puppet module, sent a pull request in github https://github.com/dprince/puppet-qpid/pull/13 pull request has been merged to upstream repository https://github.com/dprince/puppet-qpid/pull/13 Ivan, can you provide more info as to how to verify this change? where do i test that the actual value was changed from 500? db? After a successful installation check the max-connections directive in /etc/qpidd.conf grep max-connections /etc/qpidd.conf max-connections=65535 Please set this to ON_QA if it's fixed in this release. Oh I see this was missing qa_ack, that's why it was not set. I just verified the bug, so I'm setting qa_ack and changing it to verified. 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. http://rhn.redhat.com/errata/RHSA-2014-0233.html |