Is there a way to filter out the SSH unreachable (maybe not on first run) but maybe give them a specific tag; so check for error message and then I can tag those ec2 instance to filter them out next run?
Alexey Vazhnov
unread,
Jul 19, 2016, 7:40:45 AM7/19/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Ansible Project
I know only «all_instances = False» (by default) in ec2.ini, to exclude stopped.
Unreachable hosts will be skipped by Ansible, but error messages will be displayed.
Anthony Cheng
unread,
Jul 19, 2016, 8:48:45 AM7/19/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Ansible Project
For larger environment that seems a bit unwieldy; I am wondering what would be the best practice here? E.g. are people running this sort of playbook automatically every x minutes and then use the cache facts?