coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
[epic] Exclude certain Minion tasks from "Too many Minion job failures alert" alert
There are certain Minion tasks which fail regularly but there's not much we can do about it.
- #99837 All OBS rsync related tasks: Such failing tasks seem to have no impact; apparently it is sufficient if it works on the next attempt or users are able to fix problems themselves.
save_needletasks: The needles dir on OSD might just be misconfigured by the user, e.g. we recently had lots of failing jobs for a needles directory for a new distribution. The users were often able to fix the problem themselves after they see the error (which is directly visible when saving a needle).
finalize_job_resultstasks: I am not sure about this one. If the job just fails due to a user-provided hook script it should not be our business. On the other hand, we also configure the hook script for the investigation ourselves and want to be informed about problems. (So likely we want to consider these failures after all.)
- #99831 jobs failing with the result
'Job terminated unexpectedly (exit code: 0, signal: 15)': This problem is independent of the task but is of course seen much more often on task we spawn many jobs of (e.g.
finalize_job_resulttasks) and tasks with possibly long running jobs (e.g.
limit_assets). I suppose the error just means the Minion worker was restarted as signal 15 is
SIGTERM. Since such tasks are either not very important or triggered periodically we can likely just ignore those failed jobs.
Instead of implementing this on the monitoring-level we could also change openQA's behavior so these jobs are not considered failing. This would allow for a finer distinction (e.g. jobs would still fail if there's an unhanded exception due to a real regression). The disadvantage would be that all openQA instances would be affected. However, that's maybe not a bad thing and we can make it always configurable.
Since commit 60ba6e1
Author: Amrysliu firstname.lastname@example.org
Date: Wed Jan 13 14:40:19 2021 +0800
Ignore specified failed minion jobs See: https://progress.opensuse.org/issues/70768
it is possible to exclude certain minion tasks. With this it should be possible to exclude more just based on configuration
There are multiple points to be addressed. Maybe this should have been an epic. However, I agree with okurz's previous comment about getting started (#96263#note-9).
By the way, we're generating the data for InfluxDB via the openQA web application. This is not using direct SQL queries. I've recently checked the concrete code and Minion API we use so far. There seemed no easy way to do a filtered query via the Mojo API so one would have to loop through all failed jobs to filter jobs with the result
Job terminated unexpectedly out. Maybe it is simpler and more performant to query Minion's database tables directly via PostgreSQL like we already do for other monitoring data.