From 3a106f7e67e4b7f7c446058b98c33f8c71ca2868 Mon Sep 17 00:00:00 2001
From: Davanum Srinivas <dims@linux.vnet.ibm.com>
Date: Wed, 27 Mar 2013 15:17:44 -0400
Subject: [PATCH] getLogger should be called after logging is configured

logging needs to be setup properly before we try to log
something. Fixed one spot from logging->LOG

Fixes LP# 1161038

Change-Id: I87743cff9062e47c1d5e989c2c0c05c3921b65c7
---
 bin/cinder-all | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/bin/cinder-all b/bin/cinder-all
index e3c74eff8c4..e384e89c6ab 100755
--- a/bin/cinder-all
+++ b/bin/cinder-all
@@ -46,18 +46,18 @@ from cinder import service
 from cinder import utils
 
 
-LOG = logging.getLogger('cinder.all')
-
 if __name__ == '__main__':
     flags.parse_args(sys.argv)
     logging.setup("cinder")
+    LOG = logging.getLogger('cinder.all')
+
     utils.monkey_patch()
     servers = []
     # cinder-api
     try:
         servers.append(service.WSGIService('osapi_volume'))
     except (Exception, SystemExit):
-        logging.exception(_('Failed to load %s') % '%s-api' % api)
+        LOG.exception(_('Failed to load osapi_volume'))
 
     for binary in ['cinder-volume', 'cinder-scheduler']:
         try: