Since we're comparing local time to database time, we need to correctly
handle negative offsets to account for clock skew. The datetime.timedelta
class always reports a positive number of seconds, but with a possibly
negative number of *days*. Therefore, take the days into account.
Reviewed: https:/ /review. openstack. org/462602 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=f3f05c9a3f6 109ec1e102ac967 7accb82eb6cc54
Committed: https:/
Submitter: Jenkins
Branch: master
commit f3f05c9a3f6109e c1e102ac9677acc b82eb6cc54
Author: Zane Bitter <email address hidden>
Date: Thu May 4 11:41:55 2017 -0400
Deal correctly with negative elapsed time
Since we're comparing local time to database time, we need to correctly
handle negative offsets to account for clock skew. The datetime.timedelta
class always reports a positive number of seconds, but with a possibly
negative number of *days*. Therefore, take the days into account.
Change-Id: I4422e4cf41cb57 cdc89548d01b0ab c27cda914ef
Closes-Bug: #1688327