Reviewed: https://review.openstack.org/447481 Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=56ca061009d419a0866d58d5d1aecef45349bdc5 Submitter: Jenkins Branch: stable/ocata
commit 56ca061009d419a0866d58d5d1aecef45349bdc5 Author: Vladimir Sharshov (warpc) <email address hidden> Date: Fri Mar 17 20:48:52 2017 +0300
Fix wrong ready status instead of stopped for stop deployment
Report ready status for node means successful node status which can be get if all tasks was passed with ready and skipped statuses.
Same effect can be get if Astute mark node as skipped. In this case we also get equal status 'successful'.
So we need ask node about skipped statuses before ask it about successful status to prevent losing context about stop deployment operation.
Change-Id: I3c042425cab800de0bfc4e03f29414b145f44983 Closes-Bug: #1672964 (cherry picked from commit 496212798efa9f167de20a3ea0c2146658b2b466)
Reviewed: https:/ /review. openstack. org/447481 /git.openstack. org/cgit/ openstack/ fuel-astute/ commit/ ?id=56ca061009d 419a0866d58d5d1 aecef45349bdc5
Committed: https:/
Submitter: Jenkins
Branch: stable/ocata
commit 56ca061009d419a 0866d58d5d1aece f45349bdc5
Author: Vladimir Sharshov (warpc) <email address hidden>
Date: Fri Mar 17 20:48:52 2017 +0300
Fix wrong ready status instead of stopped for stop deployment
Report ready status for node means successful node status
which can be get if all tasks was passed with ready and skipped
statuses.
Same effect can be get if Astute mark node as skipped. In this
case we also get equal status 'successful'.
So we need ask node about skipped statuses before ask it about
successful status to prevent losing context about stop
deployment operation.
Change-Id: I3c042425cab800 de0bfc4e03f2941 4b145f44983 67de20a3ea0c214 6658b2b466)
Closes-Bug: #1672964
(cherry picked from commit 496212798efa9f1