Comment 7 for bug 1756921

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (stable/queens)

Reviewed: https://review.openstack.org/582638
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=c5af538d77f2db2f78399c557224f0fbfb8b3797
Submitter: Zuul
Branch: stable/queens

commit c5af538d77f2db2f78399c557224f0fbfb8b3797
Author: James Slagle <email address hidden>
Date: Mon Mar 19 12:10:18 2018 -0400

    Retry previously failed deployments

    Previously, when the server pre and post deployments were run, if one
    failed, it would not be automatically retried since the deployed file
    for the deployment exists under /var/lib/heat-config/deployed.

    This could be overridden by passing -e force=true to ansible-playbook,
    however for deployments that have previously failed, I don't think this
    should be required, and we should just retry them automatically.

    This new behavior more closely matches the traditional behavior with
    Heat, where a stack update would automatically attempt to reapply and
    deployment that was in a failed state.

    Change-Id: I18df88297abe7be50364233ed8f2514de6d3d434
    Closes-Bug: #1756921
    (cherry picked from commit 7b359af52a7d02a26ab72dfeac91e1b24c05135d)