[Openstack] Expectations for tracebacks

Lorin Hochstein lorin at isi.edu
Thu Dec 15 15:56:14 UTC 2011

I don't know if there's an official project policy, but personally I don't think an end-user should ever see a Python traceback in a logfile under normal operations (i.e., the user has configured all of the services correctly).

Lorin Hochstein, Computer Scientist
USC Information Sciences Institute

On Dec 15, 2011, at 10:49 AM, Narayan Desai wrote:

> Hello all. We've recently upgraded our cactus system to more recent
> code. In the process of doing this, we've started logging whenever we
> get tracebacks out of any of the openstack components we are running.
> Some of these are clearly bugs, while others correspond to normal
> operational conditions (like the case where all compute resources are
> occupied). My question is, what is the project position on tracebacks?
> Should they be considered to be expected, or should we be treating
> them as bugs and filing tickets/patches for them?
> thanks.
> -nld
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20111215/18f13b7c/attachment.html>

More information about the Openstack mailing list