Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1042083 - qpid exchange type "Direct" should be "direct"
qpid exchange type "Direct" should be "direct"
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-quantum (Show other bugs)
3.0
Unspecified Unspecified
high Severity high
: z4
: 3.0
Assigned To: Assaf Muller
Nir Magnezi
: ZStream
: 1043385 (view as bug list)
Depends On: 1042055 1042089
Blocks: 1024651 1042073
  Show dependency treegraph
 
Reported: 2013-12-12 15:52 EST by Russell Bryant
Modified: 2018-02-08 05:09 EST (History)
9 users (show)

See Also:
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.
Story Points: ---
Clone Of: 1042055
Environment:
Last Closed: 2014-01-30 14:50:37 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1211338 None None None Never
OpenStack gerrit 62663 None None None Never
Red Hat Product Errata RHBA-2014:0110 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform 3 bug fix advisory 2014-01-30 19:48:26 EST

  None (edit)
Description Russell Bryant 2013-12-12 15:52:31 EST
+++ 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 03:59:58 EST
*** Bug 1043385 has been marked as a duplicate of this bug. ***
Comment 3 Assaf Muller 2013-12-16 09:26:40 EST
* 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 09:48:29 EST
Ignore my last comment, wrong tab :(
Comment 5 Assaf Muller 2013-12-17 09:51:20 EST
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 14:59:04 EST
Adding >=POST to next async release
Comment 8 Nir Magnezi 2014-01-27 03:40:41 EST
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 14:50:37 EST
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.