Thanks for the suggestion. Unfortunately, this does not work. I tried your
suggestion:
- name: run ansible on all hosts in group
become: yes
hosts: nodejs
max_fail_percentage: 1
roles:
- nodejs
... as well as the 'any_errors_fatal' option, like this:
- name: run ansible on all hosts in group
become: yes
hosts: nodejs
any_errors_fatal: True
roles:
- nodejs
However, regardless of failure on the play run against nodejs, the playbook
continues running straight into the 'convert instance to ami' play:
- name: convert instance to ami
hosts: localhost
vars:
region: us-west-2
tasks:
- name: build ami
ec2_ami:
name: amlx-nodejs
description: basic nodejs image
instance_id: "{{item.id}}"
region: "{{region}}"
wait: yes
with_items: ec2.tagged_instances
Is this the way Ansible is supposed to work? Should I be separating this
out into separate playbooks and having a service like Jenkins manage
running multiple playbooks?
On Thursday, December 31, 2015 at 4:08:05 PM UTC-6, chris meyers wrote:
>
> Use ansible maximum fail percentage and set it to 1% (or 0% if 0 isn't
> treated special). This way, if any tasks fail on the play executing on the
> play running against the nodejs group, the Ami play following will not run.
> http://docs.ansible.com/ansible/playbooks_delegation.html#maximum-failure-percentage
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/46444a12-ca05-4648-910f-c233e9a70bad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
