emr-bootstrap-spark/ansible/files/bootstrap
Jeff Klukas a72d3c83cf Bug 1490400 Have telemetry.sh exit on failed commands
The existing comment about `set -e` appears to no longer apply.
I've been deploying clusters while iterating on these changes,
hitting many "Bootstrap failure" states. I have reliably been
able to find stdout.log.gz containing the relevant failure message
for these failed clusters.

There were a few commands failing for every cluster, so I had to
make some small cleanup changes in order for bootstrap to complete
with the new `set -eo pipefail` setting.
2018-12-13 13:50:49 -05:00
..
python-requirements.txt Bug 1490400 Have telemetry.sh exit on failed commands 2018-12-13 13:50:49 -05:00
pythonstartup.py Comment on bugfixes in EMR 5.16 and what we can deprecate 2018-08-14 11:41:24 -04:00
telemetry.sh Bug 1490400 Have telemetry.sh exit on failed commands 2018-12-13 13:50:49 -05:00
zeppelin-requirements.txt Rename python3-requirements.txt to zeppelin-requirements.txt 2018-06-26 12:01:16 -07:00