<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Oct 23, 2013 at 8:47 AM, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 10/23/2013 10:40 AM, John Griffith wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
<br>
<br>
On Sun, Oct 20, 2013 at 7:38 AM, Sean Dague <<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a><br></div><div class="im">
<mailto:<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>>> wrote:<br>
<br>
Dave Kranz has been building a system so that we can ensure that<br>
during a Tempest run services don't spew ERRORs in the logs.<br>
Eventually, we're going to gate on this, because there is nothing<br>
that Tempest does to the system that should cause any OpenStack<br>
service to ERROR or stack trace (Errors should actually be<br>
exceptional events that something is wrong with the system, not<br>
regular events).<br>
<br>
<br>
So I have to disagree with the approach being taken here. Particularly<br>
in the case of Cinder and the negative tests that are in place. When I<br>
read this last week I assumed you actually meant that "Exceptions" were<br>
exceptional and nothing in Tempest should cause Exceptions. It turns<br>
out you apparently did mean Errors. I completely disagree here, Errors<br>
happen, some are recovered, some are expected by the tests etc. Having<br>
a policy and especially a gate that says NO ERROR MESSAGE in logs makes<br>
absolutely no sense to me.<br>
<br>
Something like NO TRACE/EXCEPTION MESSAGE in logs I can agree with, but<br>
this makes no sense to me. By the way, here's a perfect example:<br>
<a href="https://bugs.launchpad.net/cinder/+bug/1243485" target="_blank">https://bugs.launchpad.net/<u></u>cinder/+bug/1243485</a><br>
<br>
As long as we have Tempest tests that do things like "show non-existent<br>
volume" you're going to get an Error message and I think that you should<br>
quite frankly.<br>
</div></blockquote>
<br>
Ok, I guess that's where we probably need to clarify what "Not Found" is. Because "Not Found" to me seems like it should be a request at INFO level, not ERROR.<br></blockquote><div class="gmail_default" style="font-family:'courier new',monospace">
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
ERROR from an admin perspective should really be something that would suitable for sending an alert to an administrator for them to come and fix the cloud.<br>
<br>
TRACE is actually a lower level of severity in our log systems than ERROR is.</blockquote><div><br></div><div class="gmail_default" style="font-family:'courier new',monospace">Sorry, by Trace I was referring to unhandled stack/exception trace messages in the logs.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
-Sean<br>
<br>
-- <br>
Sean Dague<br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>