Comment 5 for bug 725349

2011/3/7 Kevin L. Mitchell <email address hidden>:
> The idea here is that, in the normal case where a user has set up
> Nova, the log files contain only the actual exception information,
> minus stack traces.  That exception information can be useful to the
> user ("Hmmm, can't reach my database server, I wonder why?").  If they
> run across an actual Nova bug, on the other hand, they re-start the
> appropriate Nova service with --verbose, replicate the bug, then
> attach the stack trace.

If all you get in the log file is "An exception occurred" or perhaps "A
KeyError exception occurred", I seriously doubt you'll be able to guess
what triggered it so that you can reproduce it. Even with the stack
trace, it can be hard enough.

Can you give me an example of a stack trace that you feel should be
removed and what exactly you'd log instead?

I actually think it's extremely useful to be able to leave out --verbose
to avoid the debug information when everything is working fine, but
still get the stack trace if something actually goes wrong.

--
Soren Hansen        | http://linux2go.dk/
Ubuntu Developer    | http://www.ubuntu.com/
OpenStack Developer | http://www.openstack.org/