Nailgun tests fail time-to-time due to deployment error: task.progress 64 != 100

[Ihor Kalnytskyi]

Sometimes our tests fail, because we execute node_deletion task (which is a part of deploy supertask) before adding and committing provision and deployment tasks. That lead to the situation when receiver updates parent task and set it to 'ready', because all subtasks are ready (and we don't have provision/deployment tasks committed yet).

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/183018
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=4cd549c3721a23ff99a337063f82d0726e3d6584
Submitter: Jenkins
Branch: master

commit 4cd549c3721a23ff99a337063f82d0726e3d6584
Author: Igor Kalnitsky <email address hidden>
Date: Thu May 14 12:59:16 2015 +0300

    Send node_deletion task within other subtasks

    We have to execute node deletion task only when provision, deployment
    and other tasks are in the database. Otherwise, it may be executed
    too quickly (e.g. our tests) and this will affect parent task calculation:
    it will be marked as 'ready' because by that time it have only two
    subtasks - network_check and node_deletion - and they're ready.

    As a fix, we could send task to execution when all others tasks are
    in the database.

    Closes-Bug: #1455064

    Change-Id: I78c45959f9253ee73460259458c46c71f78434dd
    Signed-off-by: Igor Kalnitsky <email address hidden>