Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Only run the setup playbook the first time we start embedded ansible #15225

Merged
merged 2 commits into from
May 25, 2017
Merged

Only run the setup playbook the first time we start embedded ansible #15225

merged 2 commits into from
May 25, 2017

Commits on May 25, 2017

  1. Only run the setup playbook the first time we start 

    It needs to run once to put files in place and such, but
it restarts services in a way that could cause us to operate on
a running stack only to have it restart from under us.

This change makes us only run the setup playbook once so the
chance of hitting this kind of issue should be much smaller.

This effectively combines the .configure and .start methods
so that we detect when we are in the first configuration state
vs just starting up the services.

https://bugzilla.redhat.com/show_bug.cgi?id=1455063
    @carbonin
    carbonin committed May 25, 2017
    Configuration menu
    Copy the full SHA
    060a0c4 View commit details
    Browse the repository at this point in the history

  2. Don't call the .configure method as it was removed 

    https://bugzilla.redhat.com/show_bug.cgi?id=1455063
    @carbonin
    carbonin committed May 25, 2017
    Configuration menu
    Copy the full SHA
    0ec1271 View commit details
    Browse the repository at this point in the history