Bug 903547

Summary:	nova scheduler select/re-select host events upon VM boot should be info level
Product:	Red Hat OpenStack	Reporter:	Ofer Blaut <oblaut>
Component:	openstack-nova	Assignee:	David Ripton <dripton>
Status:	CLOSED WORKSFORME	QA Contact:	Yaniv Kaul <ykaul>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	2.0 (Folsom)	CC:	dripton, jkt, ndipanov, nobody
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-19 00:18:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ofer Blaut 2013-01-24 09:32:22 UTC

Description of problem:

log level of nova scheduler select/re-select host events upon VM boot should be 

info level 

currently these events are debug level in /var/log/nova/scheduler.log


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. change nova.conf to debug=true
2. create launch VM 
3. check host select or reslect (after host failed ) events are viewed under 
 /var/log/nova/scheduler.log with Info level 
  
Actual results:


Expected results:


Additional info:

Comment 2 David Ripton 2013-02-19 00:18:42 UTC

There are no remaining debug-level logging statements under nova/scheduler containing the string "select".  (The old message "No host selection for %s defined." is still in the nova/nova/locale/en_US/LC_MESSAGES/nova.po file, but it's not actually used from any Python source file.)

So this bug is obsolete.