[Bug 1472712] Re: Using SSL with rabbitmq prevents communication between nova-compute and conductor after latest nova updates

Edward Hope-Morley edward.hope-morley at canonical.com
Tue Aug 4 20:20:54 UTC 2015


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 = openstack
rabbit_password = gr6Mx2FJhC8NH3P4dBRGH8tYT39s6LLcMfJChKM6dtb3rpN5wfkRWVBcMLdhqp58
rabbit_host = 10.5.6.86
rabbit_use_ssl = True
rabbit_port = 5671
kombu_ssl_ca_certs = /etc/nova/rabbit-client-ca.pem

I've played around with reverting back to 1.3.0-0ubuntu1 (which does not
appear to exhibit the issue) and re-adding patches one-by-one and have
found that simply adding the patch for bug 1400268 causes the issue to
occur. So, question is what is it about that patch that causes these
issues?

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, 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 after latest nova updates

Status in OpenStack Compute (nova):
  Invalid
Status in oslo.messaging:
  Invalid
Status in python-oslo.messaging package in Ubuntu:
  Confirmed

Bug description:
  On the latest update of the Ubuntu OpenStack packages, it was
  discovered that the nova-compute/nova-conductor
  (1:2014.1.4-0ubuntu2.1) packages encountered a bug with using SSL to
  connect to rabbitmq.

  When this problem occurs, the compute node cannot connect to the
  controller, and this message is constantly displayed:

  WARNING nova.conductor.api [req-4022395c-9501-47cf-bf8e-476e1cc58772
  None None] Timed out waiting for nova-conductor. Is it running? Or did
  this service start before nova-conductor?

  Investigation revealed that having rabbitmq configured with SSL was
  the root cause of this problem.  This seems to have been introduced
  with the current version of the nova packages.   Rabbitmq was not
  updated as part of this distribution update, but the messaging library
  (python-oslo.messaging 1.3.0-0ubuntu1.1) was updated.   So the problem
  could exist in any of these components.

  Versions installed:
  Openstack version: Icehouse
  Ubuntu 14.04.2 LTS
  nova-conductor    1:2014.1.4-0ubuntu2.1
  nova-compute        1:2014.1.4-0ubuntu2.1
  rabbitmq-server  3.2.4-1
  openssl:amd64/trusty-security   1.0.1f-1ubuntu2.15

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1472712/+subscriptions



More information about the Ubuntu-openstack-bugs mailing list