controller0AllNodesDeployment CREATE_FAILED

[Derek Higgins]

The devtest overcloud deployment is currently not working

After a 6 hour delay heat event-list is showing
| controller0AllNodesDeployment | 551fd270-4c77-42b7-92a9-2a26f2743656 | CREATE aborted | CREATE_FAILED | 2015-02-18T07:42:48Z |

I've attached a traceback from heat thats probably the cause

Reverting this commit seems to fix the problem
https://review.openstack.org/#/c/154309/

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/156960

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/156960
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=b387a9f27ad6a36d9fb67da3ee2b647725942113
Submitter: Jenkins
Branch: master

commit b387a9f27ad6a36d9fb67da3ee2b647725942113
Author: Derek Higgins <email address hidden>
Date: Wed Feb 18 12:00:17 2015 +0000

    Revert "Move deployment handle_signal to rpc call"

    This reverts commit a63f634bfb802c03631b42de4b65e21acc4422b5.

    This commit caused a regression in tripleo-ci whith a database
    "Incorrect datetime value" error.

    Change-Id: I55f9be8ffb319edb56371d8d370d58d02bdf3867
    Closes-Bug: #1423126

[Steve Baker (steve-stevebaker)]

The integration test which I run locally (https://review.openstack.org/#/c/113711/) isn't catching this error. I will continue to investigate.

[Steve Baker (steve-stevebaker)]

It looks like the tripleo env is producing datetime objects which include tzinfo=UTC, which my local env does not. Calling timeutils.normalize_time should clean this up.