summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGary Kotton <gkotton@vmware.com>2019-04-08 01:16:04 -0700
committergaryk <gkotton@vmware.com>2019-04-15 06:50:48 +0000
commitb6b6e7bdd4064a1c216f453323a270a1c7566dbb (patch)
treeb526246d541994ca4a93218367a040729d685905
parent2a8b07b4994bda0170f1d072f266ffce375ea0cb (diff)
downloadoslo-vmware-b6b6e7bdd4064a1c216f453323a270a1c7566dbb.tar.gz
When looping call fails do not log the exception trace
This makes debugging terribly difficult when there are random legitimate errors, for example a file is not found. Change-Id: Iec76b95a70552de8e27683c0ea388b55b519db9f
-rw-r--r--oslo_vmware/common/loopingcall.py5
1 files changed, 3 insertions, 2 deletions
diff --git a/oslo_vmware/common/loopingcall.py b/oslo_vmware/common/loopingcall.py
index 489b198..c50832f 100644
--- a/oslo_vmware/common/loopingcall.py
+++ b/oslo_vmware/common/loopingcall.py
@@ -85,8 +85,9 @@ class FixedIntervalLoopingCall(LoopingCallBase):
except LoopingCallDone as e:
self.stop()
done.send(e.retvalue)
- except Exception:
- LOG.exception('in fixed duration looping call')
+ except Exception as e:
+ LOG.error('in fixed duration looping call. Error: %s',
+ str(e))
done.send_exception(*sys.exc_info())
return
else: