Comment 14 for bug 1672964

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-astute (stable/newton)

Reviewed: https://review.openstack.org/447482
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=8213652e49f0f2c28721dfb9da81ecb69d07f9c9
Submitter: Jenkins
Branch: stable/newton

commit 8213652e49f0f2c28721dfb9da81ecb69d07f9c9
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)