From aa6006d0021cc95fc20f56b8d675fea92f9e548b Mon Sep 17 00:00:00 2001 From: Takashi Kajinami Date: Tue, 25 May 2021 09:22:32 +0900 Subject: [PATCH] Remove messages very specific to CI We expect validations are used not only in upstream CI but also in actual deployments when operators want to check status of their deployments as part of daily check jobs, and having such message would confuse operators because they might not understand what that CI means and the log files mentioned are not created by TripleO. Change-Id: I1d7e1d79f4689b14a0743bd42c27baf3379f54b0 --- .../roles/service_status/tasks/containers.yaml | 6 ------ 1 file changed, 6 deletions(-) diff --git a/validations_common/roles/service_status/tasks/containers.yaml b/validations_common/roles/service_status/tasks/containers.yaml index 3817943..f1eebce 100644 --- a/validations_common/roles/service_status/tasks/containers.yaml +++ b/validations_common/roles/service_status/tasks/containers.yaml @@ -27,9 +27,6 @@ fail: msg: | Failed container detected. - On CI, please check the following locations - /var/log/extras/failed_containers.log - /var/log/extras/podman when: item is not match(".* Exited \(0\) .* ago") loop: "{{ failed_podman.stdout_lines }}" @@ -50,9 +47,6 @@ fail: msg: | Failed container detected. - On CI, please check the following locations - /var/log/extras/failed_containers.log - /var/log/extras/docker when: - failed_docker is defined - item is not match(".* Exited \(0\) .* ago")