-
Notifications
You must be signed in to change notification settings - Fork 897
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
Add a marker file for determining when the ansible setup has been run #15642
Conversation
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
3043d41
to
cd863fd
Compare
Checked commit carbonin@cd863fd with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 lib/embedded_ansible.rb
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
…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
Fine backport details:
|
…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
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