-
Committer:
Scott Moser
-
Author(s):
Joshua Harlow
-
Date:
2013-12-12 16:28:05 UTC
-
mfrom:
(861.1.1 cloud-init)
-
Revision ID:
smoser@ubuntu.com-20131212162805-dfem4u14vxypsi1k
Add a log message around import failures.
Since the import failure can be an expected failure do not log that
failure at a WARNING level, but to start log it at a DEBUG level. This
will help in figuring out why imports fail (if they ever do) for developer
and cloud-init users. Previously it is hard to know if a module fails
importing for a valid reason (not existent) or an invalid reason (the
module exists but the module has a dependency which is not satisfied).