summaryrefslogtreecommitdiff
path: root/upstart
diff options
context:
space:
mode:
authorJoshua Harlow <harlowja@gmail.com>2013-12-12 11:28:05 -0500
committerScott Moser <smoser@ubuntu.com>2013-12-12 11:28:05 -0500
commit84df36df0fbe23bf6adacd0aa531765dbda6f27a (patch)
treee707e0e0f4a575edca2ffce4cce33b88587e709d /upstart
parentee9fbafae1abfd7ba3f4bece11f722519116ca81 (diff)
parent47d15924ea38f249a2c54d33dd24c3c284c4eb72 (diff)
downloadvyos-cloud-init-84df36df0fbe23bf6adacd0aa531765dbda6f27a.tar.gz
vyos-cloud-init-84df36df0fbe23bf6adacd0aa531765dbda6f27a.zip
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).
Diffstat (limited to 'upstart')
0 files changed, 0 insertions, 0 deletions