Document where to continue from run-upgrade.sh failures

[Nolan Brubaker]

When run-upgrades.sh fails, we should communicate to users where to continue from.

In particular, the last 4 playbook executions of the script are where failures like timeouts for fetching packages are likely to happen.

We can recover from this by simply executing those playbooks again. Anything prior to that is setup work that the script should prevent itself from doing by checking for the presence of /etc/rpc_deploy/

[Kevin Carter (kevin-carter)]

Review inflight https://review.openstack.org/#/c/202821/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/202821
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=2badb5341f79fdec0e983aadf81f527a645416d8
Submitter: Jenkins
Branch: master

commit 2badb5341f79fdec0e983aadf81f527a645416d8
Author: kevin <email address hidden>
Date: Thu Jul 16 17:26:43 2015 -0500

    Fix general upgrade issues for Juno > Kilo

    This change adds a container task to ensure that container networks are up
    and using the new configs as written by the lxc-container-create play. This
    should resolve an issue where the container networks could be in a down
    state after an upgrade due to a configuration file change.

    A run function was also added to make it possible for a deployer to know
    where in the upgrade process something might have failed and the order in
    which the tasks may need to be rerun to continue the upgrade.

    Change-Id: If02c4e269375368b6f613c5a9e3c947dddbd27f9
    Closes-Bug: #1474585
    Partial-Bug: #1475727

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/204278
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=31b2edfddcea321f25d99556e3d1844fa7359b58
Submitter: Jenkins
Branch: kilo

commit 31b2edfddcea321f25d99556e3d1844fa7359b58
Author: kevin <email address hidden>
Date: Thu Jul 16 17:26:43 2015 -0500

    Fix general upgrade issues for Juno > Kilo

    This change adds a container task to ensure that container networks are up
    and using the new configs as written by the lxc-container-create play. This
    should resolve an issue where the container networks could be in a down
    state after an upgrade due to a configuration file change.

    A run function was also added to make it possible for a deployer to know
    where in the upgrade process something might have failed and the order in
    which the tasks may need to be rerun to continue the upgrade.

    Change-Id: If02c4e269375368b6f613c5a9e3c947dddbd27f9
    Closes-Bug: #1474585
    Partial-Bug: #1475727
    (cherry picked from commit 2badb5341f79fdec0e983aadf81f527a645416d8)