Reviewed: https://review.openstack.org/277378 Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=a3e19a0abe1e68daaf90cfcd6db9e6056cf10db2 Submitter: Jenkins Branch: master
commit a3e19a0abe1e68daaf90cfcd6db9e6056cf10db2 Author: Kirill Zaitsev <[email protected]> Date: Mon Feb 8 15:58:58 2016 +0300 Promote log message to exception level on artifact load failure Before this patch exact place of where the error happened during artifact load was hard to pinpoint, because it was not shown in the stacktrace. With this change exception is no longer just converted to string and printed, but also a stacktrace of exact location of the error is printed Change-Id: I1442b6743e77e2aa47a708ae1c38d7c4a54b8cd1 Closes-Bug: #1543105 ** Changed in: glance Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1543105 Title: Artifacts code conceals what/where errors happened during plugin loading Status in Glance: Fix Released Bug description: Currently exception is converted to string and we get smth like "2016-02-08 15:47:53.218 12604 ERROR glance.common.artifacts.loader [-] Could not load plugin from assets.glance_image.v1.package: __init__() got multiple values for keyword argument 'mutable' " and the stacktrace shown later conceals the place where the actual error has happened. this doesn't help much with debugging plugin code. It would be great to have relevant stacktrace printed on errors in artifact definitions. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1543105/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
