← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1371566] Re: Async conductor tasks should not raise exceptions

 

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


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

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

Title:
  Async conductor tasks should not raise exceptions

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Conductor API use cast or spawn_n to start async tasks such as
  rebuild_instance() and unshelve_instance(). Since no caller is waiting
  for a response, there is no reason for them to raise exceptions if
  anything goes wrong.

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


References