Bug 947498 - Quantum seams to be trying to connect to rabbitMQ despite being configured for QPID
Summary: Quantum seams to be trying to connect to rabbitMQ despite being configured fo...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-quantum
Version: 2.0 (Folsom)
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.0
Assignee: RHOS Maint
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-02 15:06 UTC by Paul Robert Marino
Modified: 2019-09-09 15:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-10 16:46:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Qauntum.conf to reproduce the issue (6.59 KB, application/octet-stream)
2013-04-02 15:06 UTC, Paul Robert Marino
no flags Details

Description Paul Robert Marino 2013-04-02 15:06:24 UTC
Created attachment 730839 [details]
Qauntum.conf to reproduce the issue

Description of problem:
I keep seeing this in quantums logs
"
2013-04-02 09:50:59    ERROR [quantum.openstack.common.rpc.common] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 1 seconds.
2013-04-02 09:51:00     INFO [quantum.openstack.common.rpc.common] Reconnecting to AMQP server on localhost:5672
2013-04-02 09:51:00    ERROR [quantum.openstack.common.rpc.common] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 3 seconds.
2013-04-02 09:51:03     INFO [quantum.openstack.common.rpc.common] Reconnecting to AMQP server on localhost:5672
2013-04-02 09:51:03    ERROR [quantum.openstack.common.rpc.common] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 5 seconds.
2013-04-02 09:51:08     INFO [quantum.openstack.common.rpc.common] Reconnecting to AMQP server on localhost:5672
2013-04-02 09:51:08    ERROR [quantum.openstack.common.rpc.common] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 7 seconds.
2013-04-02 09:51:15     INFO [quantum.openstack.common.rpc.common] Reconnecting to AMQP server on localhost:5672
2013-04-02 09:51:15    ERROR [quantum.openstack.common.rpc.common] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 9 seconds.
2013-04-02 09:51:24     INFO [quantum.openstack.common.rpc.common] Reconnecting to AMQP server on localhost:5672
2013-04-02 09:51:24    ERROR [quantum.openstack.common.rpc.common] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 11 seconds.
"
qpid is running on the same host as quantum server
"
netstat -tlnp |grep qpid
tcp        0      0 0.0.0.0:5672                0.0.0.0:*                   LISTEN      21954/qpidd
tcp        0      0 :::5672                     :::*                        LISTEN      21954/qpidd
"
its also trying to connect to localhost when qpid_hostname in the quantum.conf is set to the fully quallified domain name of the server.

just as a test I specified the the rabbit_host and it still cant connect but i start seeing the right hostname in the logs


Version-Release number of selected component (if applicable):

It happens with openstack-quantum-2012.2.3 and not with openstack-quantum-2012.2.1

How reproducible:

attached is a copy of the configuration

Comment 2 Paul Robert Marino 2013-04-02 16:51:20 UTC
I found what causes it the quantum configuration

this works
"
rpc_backend = quantum.openstack.common.rpc.impl_qpid
"
this breaks
"
rpc_back_end = quantum.openstack.common.rpc.impl_qpid
"

this appears to be a documentation bug upstream

http://docs.openstack.org/folsom/openstack-network/admin/content/quantum_conf.html



It does also effect 0penstack-quantum-2012.2.1

Comment 3 Russell Bryant 2013-04-10 16:46:12 UTC
Ok, so it looks like this was a configuration issue and not a bug in the code.  The documentation you refer to is upstream documentation.  You can file a bug for it here:

https://bugs.launchpad.net/openstack-manuals

Thanks!


Note You need to log in before you can comment on or make changes to this bug.