[Openstack] Expectations for tracebacks
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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Expectations for tracebacks
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 -- Lorin Hochstein, Computer Scientist USC Information Sciences Institute 703.812.3710 http://www.east.isi.edu/~lorin 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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Expectations for tracebacks
On Thu, Dec 15 2011, 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. I think all are bugs. Even if you understand some of them and considers them to be logical, you should not see ugly backtraces. You should see nice log lines any system administrator can read and understand clearly. -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Expectations for tracebacks
Definitely we should be filing bugs. Jesse On Thu, Dec 15, 2011 at 8:00 AM, Julien Danjou julien.dan...@enovance.com wrote: On Thu, Dec 15 2011, 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. I think all are bugs. Even if you understand some of them and considers them to be logical, you should not see ugly backtraces. You should see nice log lines any system administrator can read and understand clearly. -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Expectations for tracebacks
I think all are bugs. Even if you understand some of them and considers them to be logical, you should not see ugly backtraces. You should see nice log lines any system administrator can read and understand clearly. I agree. There are some other practical reasons for it too: - Exceptions change between releases (line numbers, file names, call stack, etc), so it can be hard to tell sometimes if you're looking at the same thing or different. - Exceptions take multiple lines and may actually contain the reason only in the last one. That means `grep 'CRIT|ERROR' ...` will not show the real message. - It might not be a critical situation actually. Most of exceptions will probably be, but there are also possible cases of couldn't remove X, because it's not there anymore which might be warnings. I'd be happy to see exceptions disappear completely from logs, unless something really unexpected happens - then the stacktrace and message help a lot with debugging. Regards, Stanisław Pitucha Cloud Services Hewlett Packard ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
