yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1122733] Re: XenAPI Volume Errors not showing up in Instance Faults

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Thu, 21 Feb 2013 08:51:23 -0000
Reply-to: Bug 1122733 <1122733@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => grizzly-3

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

Title:
  XenAPI Volume Errors not showing up in Instance Faults

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  When an exception is raised in the low-level volume code for xenapi,
  e.g. down in volume_utils or volumeops, it is being caught and re-
  raised as a StorageError with a relatively generic error message.

  This catching and re-raising is unnecessary and hampers debugging by
  masking the underlying exceptions from XenServer, which often are very
  helpful in troubleshooting the issue.

  This proposed solution is to remove this unnecessary exception
  handling code and instead propagate that up to the instance faults.

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