Comment 6 for bug 1675174

I did a quick sanity test to prove the heat timestamp is respected on recent heat master (3d4547f):

[stack@undercloud ~]$ heat stack-create timeout_test_3d4547f -f timeout-test.yaml -t 5
...
(undercloud) [stack@undercloud ~]$ openstack stack event list timeout_test_3d4547f --follow
2017-03-24 13:51:14Z [timeout_test_3d4547f]: CREATE_IN_PROGRESS Stack CREATE started
2017-03-24 13:51:14Z [timeout_test_3d4547f.Test]: CREATE_IN_PROGRESS state changed
2017-03-24 13:56:14Z [timeout_test_3d4547f.Test]: CREATE_FAILED CREATE aborted
2017-03-24 13:56:14Z [timeout_test_3d4547f]: CREATE_FAILED Create timed out

One other thing we probably need to check is that the event handling on failure hasn't changed, as IIRC there have been some changes to the zaqar event handling quite recently in tripleo-common and tripleoclient.