import_class() does not report original exception

Bug #820642 reported by Kevin L. Mitchell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Wishlist
Unassigned

Bug Description

The utils.import_class() function does a very handy thing, but it catches ImportError and simply raises a NotFound exception without including in the message what the original error was. This caused a problem when glance added xattr to its requirements, in that all we get is this mysterious message that "Client could not be found". It wouldn't take much to augment the "NotFound" message with the text of the original exception, which could give us a better clue as to how to fix the problem.

Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Russell Bryant (russellb) wrote :

This has already been fixed:

commit 33e58925c75b66c6800d3ba6068ee1e4f0db6617
Author: Julien Danjou <email address hidden>
Date: Thu Oct 6 17:15:32 2011 +0200

    Include original exception in ClassNotFound exception

Changed in nova:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.