commit d35f0112d955e31e5ececdea17798b5be6ead435
Author: Igor Kalnitsky <email address hidden>
Date: Thu May 5 20:09:29 2016 +0300
Fix 'reexecute_on' for pre-/post- deployment tasks
So far 'reexecute_on' for pre- and post- deployment tasks has been taken
into account only in scale-down case (when there's nothing to deploy,
only to remove). That cause a lot of trouble when it's impossible to
plugin developers to trigger some action in scale-up case.
Since now it's fixed, and 'reexecute_on' works for pre- and post-
deployment tasks in all cases.
This commit won't be merged into master and stable/9.0, since the whole
system has been rewritten during LCM story and all tasks are intended to
be reexecuted by default unless their conditions say "No".
Reviewed: https:/ /review. openstack. org/313076 /git.openstack. org/cgit/ openstack/ fuel-web/ commit/ ?id=d35f0112d95 5e31e5ececdea17 798b5be6ead435
Committed: https:/
Submitter: Jenkins
Branch: stable/8.0
commit d35f0112d955e31 e5ececdea17798b 5be6ead435
Author: Igor Kalnitsky <email address hidden>
Date: Thu May 5 20:09:29 2016 +0300
Fix 'reexecute_on' for pre-/post- deployment tasks
So far 'reexecute_on' for pre- and post- deployment tasks has been taken
into account only in scale-down case (when there's nothing to deploy,
only to remove). That cause a lot of trouble when it's impossible to
plugin developers to trigger some action in scale-up case.
Since now it's fixed, and 'reexecute_on' works for pre- and post-
deployment tasks in all cases.
This commit won't be merged into master and stable/9.0, since the whole
system has been rewritten during LCM story and all tasks are intended to
be reexecuted by default unless their conditions say "No".
Change-Id: Ib65585c8b4cff1 8444192f377545f ed82b5144da
Closes-Bug: #1569920