From b6b6e7bdd4064a1c216f453323a270a1c7566dbb Mon Sep 17 00:00:00 2001 From: Gary Kotton Date: Mon, 8 Apr 2019 01:16:04 -0700 Subject: [PATCH] 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 --- oslo_vmware/common/loopingcall.py | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/oslo_vmware/common/loopingcall.py b/oslo_vmware/common/loopingcall.py index 489b1987..c50832fa 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: