Bug 1042083 - qpid exchange type "Direct" should be "direct"
Summary: qpid exchange type "Direct" should be "direct"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-quantum
Version: 3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z4
: 3.0
Assignee: Assaf Muller
QA Contact: Nir Magnezi
URL:
Whiteboard:
: 1043385 (view as bug list)
Depends On: 1042055 1042089
Blocks: 1024651 1042073
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:52 UTC by Russell Bryant
Modified: 2019-09-09 14:44 UTC (History)
8 users (show)

Fixed In Version: openstack-quantum-2013.1.4-4.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.
Clone Of: 1042055
Environment:
Last Closed: 2014-01-30 19:50:37 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1211338 0 None None None Never
OpenStack gerrit 62663 0 None None None Never
Red Hat Product Errata RHBA-2014:0110 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform 3 bug fix advisory 2014-01-31 00:48:26 UTC

Description Russell Bryant 2013-12-12 20:52:31 UTC 
+++ This bug was initially created as a clone of Bug #1042055 +++

There's a typo in nova/openstack/common/rpc/impl_qpid.py where an exchange type of "Direct" is used where it should be "direct".
Comment 2 lpeer 2013-12-16 08:59:58 UTC 
*** Bug 1043385 has been marked as a duplicate of this bug. ***
Comment 3 Assaf Muller 2013-12-16 14:26:40 UTC 
* Setup RHOS 4.0 latest repos (2013-12-12.1)
* Installed using Packstack: One controller (Everything on it), 2 additional * compute nodes. All 3 are VMs on different physical hosts running RHEL 6.5
* Disabled firewall on controller
* SELinux is in permissive mode
* Disabled firewall on compute nodes for VNC

* In /etc/neutron/plugin.ini, for all hypervisors:
  Under [OVS]
  tenant_network_type=vxlan
  tunnel_type=vxlan
  Under [AGENT]
  tunnel_types=vxlan

* On all hypervisors:
  ovs-vsctl emer-reset && service openstack-openvswitch-agent restart

* Deleted network that was created as GRE, recreated it

I have connectivity between instances running on different hypervisors.
Comment 4 Assaf Muller 2013-12-16 14:48:29 UTC 
Ignore my last comment, wrong tab :(
Comment 5 Assaf Muller 2013-12-17 14:51:20 UTC 
Patch submitted to upstream stable/grizzly branch. If it cannot be merged, or if z-stream won't be rebased in time off upstream stable/grizzly then I'll manually backport to downstream.
Comment 6 Scott Lewis 2014-01-21 19:59:04 UTC 
Adding >=POST to next async release
Comment 8 Nir Magnezi 2014-01-27 08:40:41 UTC 
Verified NVR: python-quantum-2013.1.4-4.el6ost.noarch


Verification based on: https://review.openstack.org/#/c/62663/1/quantum/openstack/common/rpc/impl_qpid.py


1. typo is fixed:
# grep -A1 -B1 '"type": "direct"' /usr/lib/python2.6/site-packages/quantum/openstack/common/rpc/impl_qpid.py
                                             "%s/%s" % (msg_id, msg_id),
                                             {"type": "direct"},
                                             msg_id,
--
        super(DirectPublisher, self).__init__(session, msg_id,
                                              {"type": "direct"})

2. I didn't find any related errors in quantum logs.
Comment 10 errata-xmlrpc 2014-01-30 19:50:37 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-0110.html
Note You need to log in before you can comment on or make changes to this bug.