Ironic driver fails to start when CONF.ironic.client_log_level is set

[Jim Rollenhagen]

In commit 97d63d8745cd9b3b391ce96b94b4da263b3a053d, logging was changed to use oslo.log. However, the ironic driver previously interacted with the stdlib logging module to set the log level dynamically.

oslo.log does not provide the methods that were being used (getLevelName), and so this block of code causes nova-compute to fail to start when this option is set: https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L184-187

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/170221

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/170221
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d6baa2ae4d7f18dc2e4845af25c21b95767f46ef
Submitter: Jenkins
Branch: master

commit d6baa2ae4d7f18dc2e4845af25c21b95767f46ef
Author: Jim Rollenhagen <email address hidden>
Date: Thu Apr 2 10:48:24 2015 -0700

    Ironic: fix log level manipulation

    This moves log level manipulation back to the stdlib module, as oslo.log
    does not have the methods required to do this.

    Also deprecate this option, in favor of the standard logging
    configuration, to be removed in Liberty.

    Change-Id: I5c8435ddf7d6f50f367d23a2c586fafedae13cb0
    Closes-Bug: #1439796