I have the following task:
- name: Create ELK instance
ec2:
image: "{{ubuntu_image.ami}}"
region: "{{ec2_region}}"
vpc_subnet_id: "{{env_subnets.private|for_count(item)}}"
instance_type: "{{elk_instance_type}}"
assign_public_ip: false
group: "{{security_groups}}"
instance_tags:
Name: "{{env_prefix}}elk-{{item}}"
elk: "group"
env: "{{env}}"
managed_by: ansible
exact_count: 1
count_tag:
Name: "{{env_prefix}}elk-{{item}}"
key_name: "{{aws_key_name}}"
wait: yes
register: ec2_elk
with_sequence: count={{elk_instance_count}}
elk_instance_count = 1, and all the other attributes have correct values.
When I run this task the instance to be started is already running and the
task should be "ok, changed=false" with the ec2_elk register populated.
With 1.9.1, this is indeed what happens. With 1.9.2-rc2 the status is
"skipped" and the ec2_elk register is not populated.
To help me better debug, does anybody know of a reason why this behavior
should have changed?
--
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/03e23dd8-be3f-4d0d-a2f2-4e55f078aed2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
