Thanks for the input everyone. We'll start filing bugs after we triage
the tracebacks.
-nld
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https
> 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
Definitely we should be filing bugs.
Jesse
On Thu, Dec 15, 2011 at 8:00 AM, Julien Danjou
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 tr
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 ot
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 Science
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 (l
6 matches
Mail list logo