| Summary: | qpid exchange type "Direct" should be "direct" | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Russell Bryant <rbryant> |
| Component: | openstack-cinder | Assignee: | Eric Harney <eharney> |
| Status: | CLOSED ERRATA | QA Contact: | Yogev Rabl <yrabl> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.0 | CC: | eharney, ndipanov, rbryant, sclewis, sradvan, yeylon |
| Target Milestone: | z4 | Keywords: | EasyFix, ZStream |
| Target Release: | 3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-cinder-2013.1.4-5.el6ost | Doc Type: | Bug Fix |
| Doc Text: |
Cause: QPID direct publisher using the wrong exchange type 'Direct'
Consequence: If the exchange had not been created previously by a consumer, the publisher would crash because it couldn't find the specified exchange.
Fix: Change the exchange type in the Publisher to 'direct'
Result: The publisher operates as expected.
|
Story Points: | --- |
| Clone Of: | 1042055 | Environment: | |
| Last Closed: | 2014-01-30 19:50:45 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: | |
| Bug Depends On: | 1042055 | ||
| Bug Blocks: | 1024651, 1042073, 1042083 | ||
|
Description
Russell Bryant
2013-12-12 20:53:56 UTC
Adding >=POST to next async release verified on: python-cinderclient-1.0.4-1.el6ost.noarch python-cinder-2013.1.4-6.el6ost.noarch openstack-cinder-2013.1.4-6.el6ost.noarch python-qpid-0.14-11.el6_3.noarch python-qpid-0.14-11.el6_3.noarch qpid-cpp-server-0.14-22.el6_3.x86_64 qpid-cpp-client-0.14-22.el6_3.x86_64 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-0110.html |