ansible

History

Dag Wieers fceb71128e Return code is not very useful to assume a task failed So I thought I fixed it before, but there's still one location where the `rc` value is influential to decide whether a task failed or not. We already established in #24867 that it is up to the module to decide what the return code actually means, not the task executor. We modified the existing modules to move that logic into the module (eg. for command, shell, etc.) This relates to the integration tests of win_robocopy, where different return codes have different meanings: - 0 -- No files copied. - 1 -- Files copied successfully! (changed) - 2 -- Some Extra files or directories were detected. No files were copied. (warning) - 3 -- (2+1) Some files were copied. Additional files were present. (changed) - 4 -- Some mismatched files or directories were detected. Housekeeping might be required! (changed + warning) - 5 -- (4+1) Some files were copied. Some files were mismatched. (changed + warning) - 6 -- (4+2) Additional files and mismatched files exist. No files were copied. (warning) - 7 -- (4+1+2) Files were copied, a file mismatch was present, and additional files were present. (changed + warning) - 8 -- Some files or directories could not be copied! (changed + failed) - 9 - 15 -- Fatal error. Check log message! (failed) - 16 -- Serious Error! No files were copied! Do you have permissions to access $src and $dest? (failed) This also fixes #24652		9 years ago
..
module_common	test/: PEP8 compliancy (#24803 )	9 years ago
__init__.py	…
test_play_iterator.py	test/: PEP8 compliancy (#24803 )	9 years ago
test_playbook_executor.py	test/: PEP8 compliancy (#24803 )	9 years ago
test_task_executor.py	test/: PEP8 compliancy (#24803 )	9 years ago
test_task_queue_manager_callbacks.py	Remove hack for backwards compatible v2_playbook_on_start callback	9 years ago
test_task_result.py	Return code is not very useful to assume a task failed	9 years ago