]
Shlomi Zidmi commented on OVIRT-3040:
-------------------------------------
Node is back online and reachable, however something went wrong with it yesterday and
caused it to crash. I’m investigating what was the root cause for this.
[FIRING:1] InstanceUnreachable
ibm-srv03.ovirt.org
kubernetes-nodes-exporter (amd64 linux
ibm-srv03.ovirt.org true external
bare-metal-external ci)
---------------------------------------------------------------------------------------------------------------------------------------------------
Key: OVIRT-3040
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-3040
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Alertmanager_Bot
Assignee: infra
Labels:
ALERT{alertname="InstanceUnreachable",instance="ibm-srv03.ovirt.org",job="kubernetes-nodes-exporter"}
Labels:
- alertname = InstanceUnreachable
- beta_kubernetes_io_arch = amd64
- beta_kubernetes_io_os = linux
- instance =
ibm-srv03.ovirt.org
- job = kubernetes-nodes-exporter
- kubernetes_io_hostname =
ibm-srv03.ovirt.org
- node_role_kubernetes_io_compute = true
- region = external
- type = bare-metal-external
- zone = ci
Annotations:
- description =
ibm-srv03.ovirt.org of job kubernetes-nodes-exporter has been possibly
down for more than 10 minutes.
Source:
http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exp...
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100149)