XenAPI Volume Errors not showing up in Instance Faults
Bug #1122733 reported by
Rick Harris
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Rick Harris |
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.
Changed in nova: | |
assignee: | nobody → Rick Harris (rconradharris) |
status: | New → In Progress |
importance: | Undecided → High |
tags: | added: xenserver |
Changed in nova: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/21734
Review: https:/