Bug 1125997
| Summary: | Heat messaging failure using default qpid_topology_version=1 | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Scott Lewis <sclewis> | |
| Component: | openstack-heat | Assignee: | Zane Bitter <zbitter> | |
| Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.0 | CC: | augol, bholden, bperkins, ccrouch, dnavale, jpeeler, sbaker, sclewis, sdake, shardy, yeylon, zbitter | |
| Target Milestone: | z1 | Keywords: | TestOnly, ZStream | |
| Target Release: | 5.0 (RHEL 7) | |||
| Hardware: | Unspecified | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-heat-2014.1.1-2.3.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
The Qpid driver's v2 topology has been introduced to specifically address the slow growth of orphaned direct exchanges over time. By default, however, services still used the original v1 topology of the Qpid driver. The v2 topology had to be explicitly configured via the 'qpid_topology_version = 2' parameter.
With this fix, the Orchestration service's distribution configuration file (/usr/share/heat/heat-dist.conf) now contains the 'qpid_topology_version = 2' parameter. This effectively sets the Qpid driver's v2 topology as the default.
In addition, the default value in the Qpid implementation has been changed to 2 as well.
|
Story Points: | --- | |
| Clone Of: | 1124137 | |||
| : | 1127922 (view as bug list) | Environment: | ||
| Last Closed: | 2014-09-30 17:51:57 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: | 1124137 | |||
| Bug Blocks: | 1127922 | |||
|
Comment 4
Amit Ugol
2014-09-14 07:17:20 UTC
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/RHBA-2014-1345.html |