Stacks can time out before they've started with clock skew
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Zane Bitter |
Bug Description
The Stack.time_elapsed function only takes into account the seconds part of the difference between the current and start times, and ignores the days part. This can in theory cause some weird edge cases, but in practice the one in particular it will hit is that if the difference is small but negative then the delta is -1 days plus a large, positive number of seconds (*not* 0 days and a small negative number of seconds).
This can easily happen if clocks are out of sync, since we are comparing database time to local machine time. (Ideally we'd find a way to not do that.) In this case the stack will time out as soon as we try to check a resource on the server with the slow clock. Event logs may even appear to show that the timeout happened even before the action started.
tags: | removed: ocata-backport-potential |
Fix proposed to branch: master /review. openstack. org/462602
Review: https:/