Closed przemeklal closed 1 year ago
In Prometheus:
Query: ipmi_sel_command_success{juju_unit="ceph-osd/0"} Result: ipmi_sel_command_success{instance="openstack_c2eab20b-21b7-4f8e-813b-5ae038e9cbb4_ceph-osd_ceph-osd/0", job="hardware-observer-storage_0_default", juju_application="ceph-osd", juju_model="openstack", juju_model_uuid="c2eab20b-21b7-4f8e-813b-5ae038e9cbb4", juju_unit="ceph-osd/0"}
On the actual machine, we see:
$ sudo ipmi-sel --output-event-state --interpret-oem-data --entity-sensor-names ID | Date | Time | Name | Type | State | Event 1 | Sep-25-2023 | 08:16:07 | Battery VBAT | Battery | Critical | battery failed 2 | Sep-25-2023 | 08:17:42 | Battery VBAT | Battery | Critical | battery failed
However, there are no ipmi_sel_state metrics from this (or any other machine).
ipmi_sel_state
The server model is Supermicro AS -1124US-TNRP.
It might be a permissions problem.
Related to #28
Example user scenario affected by the behaviour introduced in #28:
In Prometheus:
On the actual machine, we see:
However, there are no
ipmi_sel_state
metrics from this (or any other machine).The server model is Supermicro AS -1124US-TNRP.