yahoo-eng-team team mailing list archive

[sean mooney <1990257@xxxxxxxxxxxxxxxxxx>]

This is not really unexpected.

nova like most opesntack service depends on rabbit being reliable and if
a RPC is lost then thinks can break.

fixing that is not in scope fo nova.
it would require a fundamental reacatecure to introduced tasks and track state to allows us to resend messages if we
see that the action was not performed after some time.
that is not something that we have development capstiy to do or an inclinationt to address currently.

we do not have any logs to review but i would guess there is an interval
where the compute agent is unable to receive messages form queus or
where they are lost when rabbit is stopped.

you might be able to address this by using durable or quoram queues but
that is out of scope of nova.

** Changed in: nova
   Importance: Undecided => Wishlist

** Changed in: nova
       Status: New => 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/1990257

Title:
  [OpenStack Yoga] Creating a VM is failed when stops only one rabbitmq

Status in kolla:
  New
Status in OpenStack Compute (nova):
  Opinion
Status in RabbitMQ:
  New

Bug description:
  Hi, I deploy a new OpenStack cluster (OpenStack Yoga) by kolla-ansible. Everything works fine.
  Then, I try to stop only one rabbitmq-server in cluster; after that, I can't create a new VM.

  Reproduce:
  - Deploy a new openstack cluster yoga by kolla-ansible
  - Stop random rabbitmq on one node (docker stop rabbitmq)
  - Test create new server

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