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.

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

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

Merged
merged 2 commits into from
May 25, 2017

Conversation

carbonin
Copy link
Member

@carbonin carbonin commented May 24, 2017

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

/cc @ghjm @matburt

Copy link
Member

@jrafanie jrafanie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but looks like the call sequence change broke the ansible runner spec.

@chrispy1
Copy link

@miq-bot add_label blocker

@carbonin carbonin force-pushed the dont_run_setup_script_every_time branch 2 times, most recently from 698869e to d477f2c Compare May 25, 2017 13:28
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 force-pushed the dont_run_setup_script_every_time branch from d477f2c to 0ec1271 Compare May 25, 2017 13:34
@miq-bot
Copy link
Member

miq-bot commented May 25, 2017

Checked commits carbonin/manageiq@060a0c4~...0ec1271 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
4 files checked, 0 offenses detected
Everything looks fine. ⭐

@jrafanie jrafanie merged commit 1fa4663 into ManageIQ:master May 25, 2017
@jrafanie jrafanie added this to the Sprint 62 Ending Jun 5, 2017 milestone May 25, 2017
simaishi pushed a commit that referenced this pull request May 25, 2017
Only run the setup playbook the first time we start embedded ansible
(cherry picked from commit 1fa4663)

https://bugzilla.redhat.com/show_bug.cgi?id=1455618
@simaishi
Copy link
Contributor

Fine backport details:

$ git log -1
commit 6317a223399bfa75383c998d634cdc8e64d5a23e
Author: Joe Rafaniello <jrafanie@users.noreply.github.com>
Date:   Thu May 25 10:46:43 2017 -0400

    Merge pull request #15225 from carbonin/dont_run_setup_script_every_time
    
    Only run the setup playbook the first time we start embedded ansible
    (cherry picked from commit 1fa46633ac8390e56fcd9d742ce8b60684c01f4e)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1455618

@carbonin carbonin deleted the dont_run_setup_script_every_time branch October 13, 2017 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants