action #100841
open
Improve logging for libvirt hosts
Added by szarate over 2 years ago.
Updated over 2 years ago.
Description
In #97532 this script was written to check the libvirt hosts, but along with that, the problem arises of how to know when something failed, having those notifications somewhere instead of having to log in into the server and check would be a good starting point.
Also the script is being started manually... so after a reeboot, has to be started manually, and it only is living atm in a single host...
Perhaps setting up something like https://github.com/louislam/uptime-kuma could be a good idea, as it has some connectors, while there's grafana, this could be a good chance to explore something new.
- Follows action #97532: [qe-core][sporadic] s390x jobs are failing to boot auto_review:"error: Cannot set interface flags on 'macvtap.*': Address already in use":retry added
- Follows deleted (action #97532: [qe-core][sporadic] s390x jobs are failing to boot auto_review:"error: Cannot set interface flags on 'macvtap.*': Address already in use":retry)
- Follows action #97532: [qe-core][sporadic] s390x jobs are failing to boot auto_review:"error: Cannot set interface flags on 'macvtap.*': Address already in use":retry added
- Subject changed from Improve logging for libvirt hosts to [qe-core]Improve logging for libvirt hosts
- Subject changed from [qe-core]Improve logging for libvirt hosts to Improve logging for libvirt hosts
I removed the tag as it is not something that falls within qe-core's responsabilities and more of a thing I'm thinking
- Project changed from openQA Tests to openQA Infrastructure
I review the unlabeled tickets on a daily base and I am fine with removing the label as long as it is in the sub project "openQA Infrastructure" in not in "openQA Tests" :-)
BTW it would be nice if everyone that adds a new ticket would move it to the sub project or label it accordingly. That makes triaging easier.
- Target version set to future
Also available in: Atom
PDF