-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 check_and_failed option to pacemaker_cluster module #52
Add check_and_failed option to pacemaker_cluster module #52
Conversation
In order to not set a state to a cluster while the cluster in not in the expected state we need to check it and fail, or poll until the cluster is in a required state, example: - name: Check pacemaker cluster running before upgrade pacemaker_cluster: state=online check_and_fail=true async: 30 poll: 4
Please add a changelog fragment in changelogs/fragments/. (You probably have to rebase with current |
In order to not set a state to a cluster while the cluster in not in the expected state we need to check it and fail, or poll until the cluster is in a required state, example: - name: Check pacemaker cluster running before upgrade pacemaker_cluster: state=online check_and_fail=true async: 30 poll: 4
…atbu/community.general into pacemaker/cluster/checknfailed
@felixfontein hm I rebased my fork, but I probably did mistake, I'm getting all commits from my last push :/ |
You need to update your local master first, probably, and then rebase against master. If you do |
bot_skip |
@matbu Git can be a pain sometimes, it's easy to get it into a confused state. You should be able to We have this guide for ansible/ansible https://docs.ansible.com/ansible/devel/dev_guide/developing_rebasing.html though remember that
|
@matbu i'll close the PR. Feel free to create a new one instead (or claim to reopen this if you want to rebase), thanks! |
* Applying changes made in ansible/ansible Changes were made on `grafana_dashboard` after a bugfix. Modules paramters now have forbidden keywords like `message`. See ansible/ansible#60051 * bsr: new rule in mutually_exclusive-unknown
In order to not set a state to a cluster while the
cluster in not in the expected state we need to check
it and fail, or poll until the cluster is in a required
state, example:
pacemaker_cluster: state=online check_and_fail=true
async: 30
poll: 4
SUMMARY
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION