Open Stack

On 03/11/2015 12:53 PM, Sylvain Bauza wrote:
>> Reporting on Scheduler Fails
>> ----------------------------
>>
>> Apparently, some time recently, we stopped logging scheduler fails
>> above DEBUG, and that behavior also snuck back into Juno as well
>> (https://etherpad.openstack.org/p/PHL-ops-nova-feedback L78). This
>> has made tracking down root cause of failures far more difficult.
>>
>> Action: this should hopefully be a quick fix we can get in for Kilo
>> and backport.
> It's unfortunate that failed scheduling attempts are providing only an
> INFO log. A quick fix could be at least to turn the verbosity up to WARN
> so it would be noticied more easily (including the whole filters stack
> with their results).
> That said, I'm pretty against any proposal which would expose those
> specific details (ie. the number of hosts which are succeeding per
> filter) in an API endpoint because it would also expose the underlying
> infrastructure capacity and would ease DoS discoveries. A workaround
> could be to include in the ERROR message only the name of the filter
> which has been denied so the operators could very easily match what the
> user is saying with what they're seeing in the scheduler logs.
> 
> Does that work for people ? I can provide changes for both.

Right, it definitely used to be *WARN* level in the logs.

I'll definitely help land patches to restore informative WARN messages
in the logs on scheduler failure. I think that handles the regression.

	-Sean

-- 
Sean Dague
http://dague.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 465 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150311/94e65e7f/attachment.pgp>