We extensively use the olso.db retry decorator[1], which will catch retriable exceptions (e.g. Staledataerrors, DBDeadlocks, etc) and recall the function. Either because of the loop holding a reference to the exception, or one of our outer wrappers inspecting the exception before reraising[2], the new exception summaries added in [3] result in every logging statement during the retry having irrelevant exception info added.
For an example, this line[4] is logging a StaleDataError that triggered the retry. However, that is completely irrelevant to the ongoing operation (we already log that something is being retried because of a retriable exception).
We need a way to get this to stop because it makes the logs really messy whenever there is a retry.
1. https://github.com/openstack/oslo.db/blob/master/oslo_db/api.py#L130
2. https://github.com/openstack/neutron/blob/master/neutron/db/api.py#L103
3. https://github.com/openstack/oslo.log/commit/48d284a9856dbaeb2890154bb71abc55dd0bee7a
4. http://logs.openstack.org/59/471059/2/check/gate-neutron-dsvm-fullstack-ubuntu-xenial/df11b90/logs/dsvm-fullstack-logs/TestHAL3Agent.test_keepalived_multiple_sighups_does_not_forfeit_mastership/neutron-server--2017-06-05--21-41-34-957535.txt.gz#_2017-06-05_21_42_05_746
Related fix proposed to branch: master
Review: https:/