yahoo-eng-team team mailing list archive

[Dina <dina.salem@xxxxxxxxxxxxxxxxx>]

Public bug reported:

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

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
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):
  New

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