| commit | eb09398678229842f23be128ac01ed2b53d2e3a8 | [log] [tgz] |
|---|---|---|
| author | Monty Taylor <mordred@inaugust.com> | Wed Aug 30 19:16:21 2017 -0500 |
| committer | Monty Taylor <mordred@inaugust.com> | Thu Aug 31 15:50:00 2017 -0500 |
| tree | 88b98d2efd7ef46bfebcda4b30691353b0994bef | |
| parent | 0d254d547198305d3d05f0cf5a24a376cfd8b782 [diff] |
Handle logging ansible python errors properly If an exception is thrown from ansible, we don't log it properly. Add a playbook to the functional test of logging that doesn't mask failures (it lets the tasks report as failed) So that we cover all four possibilities for ansible module failure exception: * failed task * failed task in item * failed task that reports as success * failed task in item that reports as success Change-Id: I9e355350f5ec34251f5030eaaa3f4bb7b4438a6e