yahoo-eng-team team mailing list archive

[Russell Bryant <922067@xxxxxxxxxxxxxxxxxx>]

I think the current behavior isn't that bad.  Every other service
connects to the message broker on startup because that's when it needs
it.  nova-api will connect only when needed, since not all requests
require it.  Nova is going to be completely busted if it's not up, so
it's pretty hard to miss and should be monitored for anyway.

It's been over a year since this was filed, so I'm going to move into
the older queue of requests (Opinion / Wishlist) in case someone would
like to pick it up later.

** Changed in: nova
       Status: Confirmed => Opinion

-- 
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/922067

Title:
  connection to RabbitMQ should be created directly after start of
  services

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  i tested starting nova-api with wrong credentials for RabbitMQ.
  service started without problems. the first errors regarding failed
  connections to the RabbitMQ service came up after trying to start a
  new instance. other operations, like listing instances, seems to work
  without RabbitMQ.

  i think all necessary connections to external services should be
  checked during the starting procedure of a service and not initial
  before the first use of the external service.

  for example after scheduling the creation of a new instance i can see
  the error in the logs, i have to fix nova.conf and afterward i have to
  restart the nova-api service. but looks like the scheduled instance is
  stucked after the restart of nova-api (now with working RabbitMQ
  credentials), the instance is in state "scheduling" forever (maybe
  that's a second bug, not sure about that).

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