James Cammarata ca5b361ad8 Reworking iterator logic regarding failed states during always ... Previous changes addressed a corner case, which unfortunately introduced another bug. This patch adds a new flag to the host state (did_rescue) which is set to true when the rescue portion of a block completes. This flag is then checked in _check_failed_state() when the fail_state != FAILED_NONE. This lead to the discovery of another bug - current strategies are not advancing hosts to ITERATING_COMPLETE after doing a peek at the next task, leaving the host state in the run_state of the final task. To address this, before gathering the list of failed hosts in StrategyBase.run(), a final pass through the iterator for all hosts is done to ensure each host is in its final state. This way, no strategy derived from StrategyBase has to worry about it and it's handled. Fixes #17983		2016-11-16 10:21:46 -06:00
..
action	corrected service filtered option to singular	2016-11-16 10:12:47 -05:00
cache	Remove direct calls to print and cleanup imports	2016-11-07 17:12:36 -05:00
callback	ansible-logstash-callback (#18282)	2016-11-08 11:17:05 -05:00
connection	ANSIBLE_SSH_CONTROL_PATH_DIR option added (#18342)	2016-11-03 15:19:59 -07:00
filter	Add 'type' filter for display the underlying python type of a variable (#18242)	2016-10-31 13:36:24 -07:00
lookup	ini lookup: add 'default' to the list of parsed keys	2016-11-08 11:07:33 -05:00
shell	Move uses of to_bytes, to_text, to_native to use the module_utils version (#17423)	2016-09-06 22:54:17 -07:00
strategy	Reworking iterator logic regarding failed states during always	2016-11-16 10:21:46 -06:00
test	restored 'results' filters	2016-10-13 13:21:40 -04:00
vars	Making the switch to v2	2015-05-03 21:47:26 -05:00
__init__.py	Filter out internal magic and connection variables from facts returns	2016-10-24 17:27:43 -05:00