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

Add a marker file for determining when the ansible setup has been run #15642

Conversation

carbonin
Copy link
Member

This ensures that we have a definitive way to determine if we have successfully run the setup for embedded ansible on a particular server

Before this change, the thread running the setup could be killed and when we tried to start the service again, we would see #configured? as true even if we didn't run through the whole playbook.

Now, we will not write this marker file until we finish running the playbook so the next worker will know to attempt the setup if the previous one was killed.

https://bugzilla.redhat.com/show_bug.cgi?id=1474427

This ensures that we have a definitive way to determine if we have
successfully run the setup for embedded ansible on a particular server

Before this change, the thread running the setup could be killed
and when we tried to start the service again, we would see #configured?
as true even if we didn't run through the whole playbook.

Now, we will not write this marker file until we finish running
the playbook so the next worker will know to attempt the setup if
the previous one was killed.

https://bugzilla.redhat.com/show_bug.cgi?id=1474427
@carbonin carbonin force-pushed the add_complete_marker_for_embedded_ansible_setup branch from 3043d41 to cd863fd Compare July 24, 2017 20:42
@miq-bot
Copy link
Member

miq-bot commented Jul 24, 2017

Checked commit carbonin@cd863fd with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
2 files checked, 1 offense detected

lib/embedded_ansible.rb

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.

:shipit:

Copy link
Member

@gtanzillo gtanzillo left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@gtanzillo gtanzillo added this to the Sprint 65 Ending Jul 24, 2017 milestone Jul 24, 2017
@gtanzillo gtanzillo merged commit 9e0fe66 into ManageIQ:master Jul 24, 2017
simaishi pushed a commit that referenced this pull request Jul 25, 2017
…ded_ansible_setup

Add a marker file for determining when the ansible setup has been run
(cherry picked from commit 9e0fe66)

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

Fine backport details:

$ git log -1
commit 71117ec97a6dbeaabf1182506234328cf7b58100
Author: Gregg Tanzillo <gtanzill@redhat.com>
Date:   Mon Jul 24 17:41:58 2017 -0400

    Merge pull request #15642 from carbonin/add_complete_marker_for_embedded_ansible_setup
    
    Add a marker file for determining when the ansible setup has been run
    (cherry picked from commit 9e0fe661bad46fee20b26e5c58114e1a8b85b6b8)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1474835

@carbonin carbonin deleted the add_complete_marker_for_embedded_ansible_setup branch October 13, 2017 19:38
d-m-u pushed a commit to d-m-u/manageiq that referenced this pull request Jun 6, 2018
…or_embedded_ansible_setup

Add a marker file for determining when the ansible setup has been run
(cherry picked from commit 9e0fe66)

https://bugzilla.redhat.com/show_bug.cgi?id=1474835
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.

5 participants