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>
Reviewed: https:/ /review. openstack. org/183018 /git.openstack. org/cgit/ stackforge/ fuel-web/ commit/ ?id=4cd549c3721 a23ff99a337063f 82d0726e3d6584
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4cd549c3721a23f f99a337063f82d0 726e3d6584
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: I78c45959f9253e e73460259458c46 c71f78434dd
Signed-off-by: Igor Kalnitsky <email address hidden>