Timeline for How do I run ansible on one host at a time and break on a failure
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 2, 2017 at 22:10 | history | edited | Woodland | CC BY-SA 3.0 |
changed the wording to better suit a recent edit in the question
|
| Mar 2, 2017 at 21:41 | comment | added | Peter Turner♦ | Heh, so I'm not the only one who is constantly patching the source. That's good to know. | |
| Mar 2, 2017 at 21:21 | comment | added | Woodland | So many bugs, in fact, that you are missing the .retry files in 2.0! github.com/ansible/ansible/issues/13944 | |
| Mar 2, 2017 at 21:20 | comment | added | Woodland | That's correct, serial: 1 should have that behavior, and if it doesn't (because ??) add max_failure_percentage: 0, too. I'd also suggest upgrading Ansible as 2.0 had a lot of bugs. | |
| Mar 2, 2017 at 21:16 | comment | added | Peter Turner♦ | Yeah, I know that ansible 2.0 will continue to run on other hosts if it gets failures on one of 'em. I guess I didn't think it would have different behavior if I ran serial:1. Is that what you're saying? | |
| Mar 2, 2017 at 21:13 | history | edited | Woodland | CC BY-SA 3.0 |
added retry answer
|
| Mar 2, 2017 at 21:04 | comment | added | Woodland | If anyone has a better sense of what happened to the change/bug in 1.9 and 2.0 please let me know and I'll update this answer. | |
| Mar 2, 2017 at 21:03 | history | answered | Woodland | CC BY-SA 3.0 |