Title: ibm storwize: Fix missing data when monitoring nodes
Class: fix
Compatible: compat
Component: checks
Date: 1704272720
Edition: cre
Level: 1
Version: 2.2.0p18
lsnodestats command was used for monitoring nodes in IBM Storwize devices.
Storwize devices don't have the lsnodestats command which led to missing data
in ibm_svc_nodestats services.
Now, the IBM SVC agent uses the lsnodestats if it's available and lsnodecanisterstats
otherwise.
[//]: # (werk v2)
# ibm storwize: Fix missing data when monitoring nodes
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-01-03T09:05:20+00:00
level | 1
class | fix
component | checks
edition | cre
lsnodestats command was used for monitoring nodes in IBM Storwize devices.
Storwize devices don't have the lsnodestats command which led to missing data
in ibm_svc_nodestats services.
Now, the IBM SVC agent uses the lsnodestats if it's available and lsnodecanisterstats
otherwise.
Title: "Cisco Devices: Temperature Sensors" used wrong lower device levels
Class: fix
Compatible: compat
Component: checks
Date: 1702899571
Edition: cre
Level: 1
Version: 2.1.0p38
The services picked the device levels meant for a "less than" comarison,
when in fact comparing "less or equal" (as Checkmk usually does).
They now pick the levels meant for "less or equal" comparison.
Title: "Cisco Devices: Temperature Sensors" used wrong lower device levels
Class: fix
Compatible: compat
Component: checks
Date: 1702899571
Edition: cre
Level: 1
Version: 2.2.0p18
The services picked the device levels meant for a "less than" comarison,
when in fact comparing "less or equal" (as Checkmk usually does).
They now pick the levels meant for "less or equal" comparison.
[//]: # (werk v2)
# "Cisco Devices: Temperature Sensors" used wrong lower device levels
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2023-12-18T11:39:31+00:00
level | 1
class | fix
component | checks
edition | cre
The services picked the device levels meant for a "less than" comarison,
when in fact comparing "less or equal" (as Checkmk usually does).
They now pick the levels meant for "less or equal" comparison.
[//]: # (werk v2)
# primekey_fan: rename service description to 'Primekey Fan'
key | value
---------- | ---
date | 2023-12-20T09:43:06+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
You are affected by this change if you monitor a Primekey appliance and use
searches or rules that rely on the service description.
In order to unify the primeky checks `primekey_fan` services description was
renamed from 'Fan Primekey' to 'Primekey Fan'.
Title: host_config: 500 status code with no explicit IPMI credentials configured
Class: fix
Compatible: compat
Component: rest-api
Date: 1702993286
Edition: cre
Level: 1
Version: 2.2.0p18
When calling the <code>host_config/collections/all</code> endpoint with IPMI credentials activated and set
to <code>No explicit credentials</code> the endpoint returns a status 500 (Internal Server Error).
Now the information is correctly returned.