Finally got to the bottom of this. The issue lies in python-amqp rather
than python-oslo.messaging. The current trusty version of python-amqp
(1.3.3) has a bug that is fixed in 1.4.4 (see
http://amqp.readthedocs.org/en/latest/changelog.html#version-1-4-4). I
tried backporting the Juno/Utopic
OK upon further investigation i have found some trace of a root cause.
Oslo.messaging always uses a timeout of 1 second when polling queues and
connections. This appears to be too small when using ssl and frequently
results in SSLError/timeout which cause all threads to fail and
reconnect and fail
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-oslo.messaging in Ubuntu.
https://bugs.launchpad.net/bugs/1472712
Title:
Using SSL with rabbitmq prevents communication between nova-compute
and conductor
A bit more info from my end. I've been trying out different scenarios
and it seems that this is constrained to Trusty Icehouse using python-
oslo.messaging version 1.3.0-0ubuntu1.2 configured to connect to
rabbitmq-server using ssl e.g. my nova.conf has:
rabbit_userid = nova
rabbit_virtual_host =
** Also affects: python-oslo.messaging (Ubuntu)
Importance: Undecided
Status: New
** Changed in: oslo.messaging
Status: Confirmed = Invalid
** Changed in: nova
Status: New = Invalid
** Changed in: python-oslo.messaging (Ubuntu)
Status: New = Confirmed
--
You
