Browse Source

[Train-Only] Instruct container-status validation to accept 137, 142 and 143 exit code status

This patch makes the validations aware of those exit code status and
accept them as not a validation failure.

Below, the upstream patches for tripleo-ansible[1] and paunch[2]:

[1] - https://review.opendev.org/q/I8f19a80016a67ccad0371c5d108516aec640f031
[2] - https://review.opendev.org/q/Iffcfc8bd18a999ae6921a4131d40241df40050f1

Related-bz: rhbz#2001629

Signed-off-by: Gael Chamoulaud (Strider) <gchamoul@redhat.com>
Change-Id: Ibd61e6ad758d4e552e5e607f45fbce75f65eed62
changes/93/824693/1
Gael Chamoulaud (Strider) 4 months ago
parent
commit
91d7a3537f
No known key found for this signature in database
GPG Key ID: 4119D0305C651D66
  1. 2
      roles/container_status/tasks/main.yaml

2
roles/container_status/tasks/main.yaml

@ -54,5 +54,5 @@
- name: Fail if we detect failed containers
fail:
msg: "Failed container detected: {{ item }}."
when: item is not match(".* Exited \(0\) .* ago")
when: item is not match(".* Exited \((0|137|142|143)\) .* ago")
loop: "{{ failed_containers.stdout_lines }}"

Loading…
Cancel
Save