[devops] zabbix trigger for fuel ci failures
Bug #1320861 reported by
Aleksandra Fedorova
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Wishlist
|
Pawel Brzozowski |
Bug Description
We need to monitor jobs on Fuel CI and trigger the alert if certain job $JOB_NAME fails $COUNT times on particular node $NODE_NAME.
I.e. if master_
Changed in fuel: | |
importance: | Undecided → Wishlist |
summary: |
- zabbix triger for fuel ci failures + zabbix trigger for fuel ci failures |
Changed in fuel: | |
status: | New → Triaged |
Changed in fuel: | |
assignee: | nobody → Fuel DevOps (fuel-devops) |
tags: | added: zabbix |
summary: |
- zabbix trigger for fuel ci failures + [devops] zabbix trigger for fuel ci failures |
Changed in fuel: | |
milestone: | 5.1 → 6.0 |
Changed in fuel: | |
milestone: | 6.0 → 6.1 |
tags: | added: non-release |
Changed in fuel: | |
milestone: | 6.1 → 7.0 |
To post a comment you must log in.
Idea is great, however: fuellib_ review_ systest_ centos job fails 3 times in a row on fuel-jenkins3, we should probably take fuel-jenkins3 out of the test node pool.
> I.e. if master_
it can happen with patchsets which fail. So to determine if server is bad, we need to run such a patch or code on it, which is known to work well (or recheck one of recently passed patches, but I'm in a favor of first option)