Bug 1124137
Summary: | Heat messaging failure using default qpid_topology_version=1 | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Brent Holden <bholden> | |
Component: | openstack-heat | Assignee: | Jeff Peeler <jpeeler> | |
Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 4.0 | CC: | bperkins, breeler, ccrouch, sbaker, sclewis, sdake, shardy, yeylon, zbitter | |
Target Milestone: | z5 | Keywords: | ZStream | |
Target Release: | 4.0 | |||
Hardware: | Unspecified | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | openstack-heat-2013.2.3-4.el6ost | 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: | ||||
: | 1125997 (view as bug list) | Environment: | ||
Last Closed: | 2014-10-22 17:52:53 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: | 1125997, 1127922 |
Description
Brent Holden
2014-07-29 04:18:34 UTC
We should probably update the default in the code, not just in the config file. See also bug 1030658 (same issue in Nova & others). Also fixed in: openstack-heat-2014.1.1-2.3.el6ost openstack-heat-2014.1.1-2.3.el7ost tested in 2013.2.4-1.el6ost 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://rhn.redhat.com/errata/RHSA-2014-1687.html |