integrate elastic recheck into tempest email results
Bug #1736272 reported by
wes hayutin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Incomplete
|
Medium
|
Arx Cruz | ||
Bug Description
integrate elastic recheck into tempest email results.
For example, if a particular error is already in elastic recheck do not send emails to notify users of the failure.
Revision history for this message
| Tom Barron (tpb) wrote | #1 |
| Changed in tripleo: | |
| assignee: | nobody → Arx Cruz (arxcruz) |
| Changed in tripleo: | |
| milestone: | queens-3 → queens-rc1 |
| Changed in tripleo: | |
| milestone: | queens-rc1 → rocky-1 |
| Changed in tripleo: | |
| milestone: | rocky-1 → rocky-2 |
| Changed in tripleo: | |
| milestone: | rocky-2 → rocky-3 |
| Changed in tripleo: | |
| milestone: | rocky-3 → rocky-rc1 |
| Changed in tripleo: | |
| milestone: | rocky-rc1 → stein-1 |
| Changed in tripleo: | |
| milestone: | stein-1 → stein-2 |
| Changed in tripleo: | |
| milestone: | stein-2 → stein-3 |
| Changed in tripleo: | |
| milestone: | stein-3 → train-1 |
| Changed in tripleo: | |
| milestone: | train-1 → train-2 |
| Changed in tripleo: | |
| milestone: | train-2 → train-3 |
| Changed in tripleo: | |
| milestone: | train-3 → ussuri-1 |
| Changed in tripleo: | |
| milestone: | ussuri-1 → ussuri-2 |
| Changed in tripleo: | |
| milestone: | ussuri-2 → ussuri-3 |
| Changed in tripleo: | |
| milestone: | ussuri-3 → ussuri-rc3 |
| Changed in tripleo: | |
| status: | Triaged → Incomplete |
| Changed in tripleo: | |
| milestone: | ussuri-rc3 → victoria-1 |
| Changed in tripleo: | |
| milestone: | victoria-1 → victoria-3 |
To post a comment you must log in.
This is all about increasing the signal to noise ratio so that these emails don't simply get ignored. Notification via email is tricky in and of itself given our time pressures and the amount of spam all of us receive. If SMEs in the various DFGs stop working on their original jobs to chase one of these issues only to find that it's e.g. a timeout due to a slow node or an infra scheduling problem then they are less likely to come back and do the right thing the next time they get such a notification.