yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #16552
[Bug 1054501] Re: Fail safe wsgi logging
The first thing we do is log the exception. This happens before we
attempt to return any information to the client or do any other
processing. So I don't think we need any other fallback. Unless you have
a testcase which demonstrates this is necessary.
** Changed in: nova
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1054501
Title:
Fail safe wsgi logging
Status in Cinder:
In Progress
Status in OpenStack Compute (Nova):
Won't Fix
Bug description:
If there are any uncaught exceptions from api controllers, they are
handled in nova/api/openstack/__init__.py:FaultWrapper, logged the
handled exception and HTTP 500 response is sent to the client.
There could be error while logging these uncaught exceptions and we
missout them in the nova logs. In such a case, these exceptions should
be logged into syslog for further investigation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1054501/+subscriptions