Comment 6 for bug 708822

the fundamental problem here is that comparison is performed between time on machine where API server running vs time where SQL is running. We just experienced exactly the same issue with scheduler, where node was off a bit...

We either need to have a strict requirement to have clocks on all nodes synchronized or to implement a fix on sqlalchemy.api level - updated/created times wil be set and verified always on the same machine.