tripleo-heat-templates/common
Emilien Macchi 7d1cd360d8 container-puppet: SystemExit with RC 1 to actually error out
Raising SystemExit() isn't enough to stop the deployment, we also need
to provide a return code:
https://docs.python.org/3.7/library/exceptions.html#SystemExit

Default is None, so we didn't exit the right return code.

With that patch, if a container failed to be configured; we will raise
an error and actually exit(1).

Change-Id: Ie4ab2ffed5e04f87c866b0d4f3e5c702a98be5ad
2019-12-09 18:31:43 -05:00
..
services Convert firewall rules to use TripleO-Ansible 2019-11-18 15:40:22 -06:00
container_startup_configs_tasks.yaml Do not log startup config output 2019-11-04 14:39:44 -07:00
container-puppet.py container-puppet: SystemExit with RC 1 to actually error out 2019-12-09 18:31:43 -05:00
container-puppet.sh Drop file test before removal 2019-11-22 10:22:39 -07:00
deploy-steps-tasks-step-0.j2.yaml Ensure we set proper SELinux label on container-puppet.sh 2019-11-28 17:01:05 +01:00
deploy-steps-tasks-step-1.yaml Mode 0750 for /var/log/containers 2019-11-04 11:06:44 +01:00
deploy-steps-tasks.yaml deploy-steps-tasks/containers: set concurrency to 2 2019-12-09 02:57:47 +00:00
deploy-steps.j2 Merge "Re-enable "service_names" hieradata" 2019-12-06 09:04:03 +00:00
post.j2.yaml Consolidate puppet/docker deployments with one deploy steps workflow 2017-08-11 17:25:02 +00:00