Fix leftover Timeout effecting most eventlet calls
When registering a new eventlet.timeout.Timeout object, eventlet
automatically starts a timer for most (if not all) future eventlet
calls. Normally, eventlet codes do not hold a timeout unless such a
timeout is used or a specific timeout length is specified through
the API, but once a Timeout object is initialized, it is left there
unless canceled.
This change fixes an un-canceled Timeout which causes some
functional tests to fail, reintroduces a fix for bug #1358206,
which was written prior to discovering the uncanceled timeout, and
increases the timeout of a test that depended on this timeout.
Reviewed: https:/ /review. openstack. org/119001 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=fdf0fa8b435 37bbd5ab6e1a2e5 5f694b77209a00
Committed: https:/
Submitter: Jenkins
Branch: master
commit fdf0fa8b43537bb d5ab6e1a2e55f69 4b77209a00
Author: John Schwarz <email address hidden>
Date: Thu Sep 4 11:34:29 2014 +0300
Fix leftover Timeout effecting most eventlet calls
When registering a new eventlet. timeout. Timeout object, eventlet
automatically starts a timer for most (if not all) future eventlet
calls. Normally, eventlet codes do not hold a timeout unless such a
timeout is used or a specific timeout length is specified through
the API, but once a Timeout object is initialized, it is left there
unless canceled.
This change fixes an un-canceled Timeout which causes some
functional tests to fail, reintroduces a fix for bug #1358206,
which was written prior to discovering the uncanceled timeout, and
increases the timeout of a test that depended on this timeout.
Closes-bug: #1358206 5894eecd8b477d7 87763edbd02
Related-bug: #1364171
Change-Id: I1bfc5af6917c52