Since change I1f1d9c0d6e3f04f1ecd5ef7c5d813005ee116409 we are running
parts of the backups on native threads, which due to an eventlet bug [1]
have bad interactions with greenthreads, so we have to avoid any logging
when executing code in a native thread.
This patch removes the MD5 logging on the SwiftObjectWriter close
method and adds comments and docstring referring to this limitation.
Reviewed: https:/ /review. openstack. org/537437 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=c6cb84bd631 35d62ccd7ed9b23 b245c41e9f105c
Committed: https:/
Submitter: Zuul
Branch: master
commit c6cb84bd63135d6 2ccd7ed9b23b245 c41e9f105c
Author: Gorka Eguileor <email address hidden>
Date: Wed Jan 24 17:00:19 2018 +0100
Remove logging on Swift backup obj writer
Since change I1f1d9c0d6e3f04 f1ecd5ef7c5d813 005ee116409 we are running
parts of the backups on native threads, which due to an eventlet bug [1]
have bad interactions with greenthreads, so we have to avoid any logging
when executing code in a native thread.
This patch removes the MD5 logging on the SwiftObjectWriter close
method and adds comments and docstring referring to this limitation.
[1] https:/ /github. com/eventlet/ eventlet/ issues/ 432
Closes-Bug: #1745168 ee7e3e9bd6e15f4 987ede4d653
Change-Id: I0857cecd7d8ab0