Bug 903547 - nova scheduler select/re-select host events upon VM boot should be info level
Summary: nova scheduler select/re-select host events upon VM boot should be info level
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 2.0 (Folsom)
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: David Ripton
QA Contact: Yaniv Kaul
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-24 09:32 UTC by Ofer Blaut
Modified: 2019-09-09 15:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-19 00:18:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.