From c2c3f3a683289fa5bac03cb423fb9d11ddb3becf Mon Sep 17 00:00:00 2001
From: Sorin Sbarnea <ssbarnea@redhat.com>
Date: Mon, 17 Dec 2018 12:03:04 +0000
Subject: [PATCH] Identify *POST* timeout failures individually

Ability to identify only POST timeout failuse is critical because in
most cases this is an infra/ci related issue which has nothing to do
with the change itself.

As opposed to normal timeouts, this needs more attention from CI/infra
because almost for sure it means missing or partial logs.

Also changes original query so they would not overlap.

Change-Id: I3b112d4784c0f7dd57a26d08335c3cbe374eb90e
LogStash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%20%5C%22POST-RUN%20END%20RESULT_TIMED_OUT%5C%22%20AND%20tags%3A%20%5C%22console%5C%22%20AND%20voting%3A1
Related-Bug: 1807940
---
 queries/1686542.yaml | 1 +
 queries/1807940.yaml | 3 +++
 2 files changed, 4 insertions(+)
 create mode 100644 queries/1807940.yaml

diff --git a/queries/1686542.yaml b/queries/1686542.yaml
index 2ef6fe29..a1d0a1a9 100644
--- a/queries/1686542.yaml
+++ b/queries/1686542.yaml
@@ -2,4 +2,5 @@ query: >-
   (message: "FAILED with status: 137" OR
   message: "FAILED with status: 143" OR
   message: "RUN END RESULT_TIMED_OUT") AND
+  NOT message:"POST-RUN END RESULT_TIMED_OUT" AND
   tags: "console"
diff --git a/queries/1807940.yaml b/queries/1807940.yaml
new file mode 100644
index 00000000..77e833eb
--- /dev/null
+++ b/queries/1807940.yaml
@@ -0,0 +1,3 @@
+query: >-
+  message: "POST-RUN END RESULT_TIMED_OUT" AND
+  tags: "console"