← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1794706] Re: The instance left stuck when oslo.messaging raised MessageDeliveryFailure exception

 

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

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

Title:
  The instance left  stuck when oslo.messaging raised
  MessageDeliveryFailure exception

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Description
  ===========
  Currently, nova use message queue such as rabbitmq to communicate between services. When booting an instance, nova api send creating message to nova conductor, unfortunately the rabbitmq is unnormal and raised MessageDeliveryFailure exception, the process is aborted and instance left stuck. so we should catch this exception and delete this instance.

  Steps to reproduce
  ==================
  1. Rabbitmq is unnormal
  2. Boot an instance.

  Expected result
  ===============
  The instance boot failed and the instance is deleted.

  Actual result
  =============
  The instance is stunk in scheduling state.

  Environment
  ===========
  1. Nova Pike
  [root@cdpm01 ~]# nova --version
  9.1.1

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


References