[//]: # (werk v2)
# agent_netapp_ontap: KeyError: 'rpm' and KeyError: 'temperature'
key | value
---------- | ---
date | 2024-08-01T14:51:58+00:00
version | 2.3.0p13
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This change affects users, which monitor NetApp via Ontap REST API. Previously,
the special agent could crash with the following error:
```
File "/omd/sites/nyccheckmk2/lib/python3/cmk/special_agents/agent_netapp_ontap.py", line 28, in write_section
for element in generator:
File "/omd/sites/nyccheckmk2/lib/python3/cmk/special_agents/agent_netapp_ontap.py", line 471, in fetch_fans
rpm=fan["rpm"],
~~^^^^^^^
KeyError: 'rpm'CRIT
```
This would occur, if either a fan or temperature sensor had an error, and thus
did not report any rpm/temperature value. This has been fixed.
[//]: # (werk v2)
# Custom graphs: Respect "Metrics with all zero values" setting
key | value
---------- | ---
date | 2024-08-05T06:51:13+00:00
version | 2.3.0p13
class | fix
edition | cee
component | multisite
level | 1
compatible | yes
The custom graph setting _Metrics with all zero values_ was not persisted and not taken into account
when rendering the graph.
Werk 17206 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# omd update: Log "Verifying site configuration"
key | value
---------- | ---
date | 2024-08-05T08:59:03+00:00
version | 2.3.0p13
class | fix
edition | cre
component | omd
level | 1
compatible | yes
If a user runs `omd update`, then the output is written to both `$OMD_ROOT/var/log/update.log` and
stdout. However, the output of site configuration verification
<a href="https://checkmk.com/werk/16408"> Werk #16408</a> was missing. This has been fixed.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# omd update: Log "Verifying site configuration"
key | value
---------- | ---
date | 2024-08-05T08:59:03+00:00
- version | 2.3.0p12
? ^
+ version | 2.3.0p13
? ^
class | fix
edition | cre
component | omd
level | 1
compatible | yes
If a user runs `omd update`, then the output is written to both `$OMD_ROOT/var/log/update.log` and
stdout. However, the output of site configuration verification
<a href="https://checkmk.com/werk/16408"> Werk #16408</a> was missing. This has been fixed.
Werk 16889 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# ewon: KeyError (device)
key | value
---------- | ---
date | 2024-08-06T07:48:07+00:00
version | 2.3.0p12
class | fix
edition | cre
component | checks
level | 1
compatible | yes
An existing rule for `check_ewon` without the mandatory key `device` would result in an exception
`KeyError (device)`.
This change makes the check function use a default, if `device` is not set.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# ewon: KeyError (device)
key | value
---------- | ---
date | 2024-08-06T07:48:07+00:00
- version | 2.3.0p13
? ^
+ version | 2.3.0p12
? ^
class | fix
edition | cre
component | checks
level | 1
compatible | yes
An existing rule for `check_ewon` without the mandatory key `device` would result in an exception
`KeyError (device)`.
This change makes the check function use a default, if `device` is not set.
Werk 16890 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# check_ewon: ValueError (incomplete format)
key | value
---------- | ---
date | 2024-08-06T07:52:50+00:00
version | 2.3.0p12
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Formatting a value with unit `%` would result in an invalid format-string making `check_ewon`
crash with an exception `ValueError (incomplete format)`.
This change makes `check_ewon` use f-formatting instead of `%`-formatting.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# check_ewon: ValueError (incomplete format)
key | value
---------- | ---
date | 2024-08-06T07:52:50+00:00
- version | 2.3.0p13
? ^
+ version | 2.3.0p12
? ^
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Formatting a value with unit `%` would result in an invalid format-string making `check_ewon`
crash with an exception `ValueError (incomplete format)`.
This change makes `check_ewon` use f-formatting instead of `%`-formatting.
[//]: # (werk v2)
# ewon: KeyError (device)
key | value
---------- | ---
date | 2024-08-06T07:48:07+00:00
version | 2.3.0p13
class | fix
edition | cre
component | checks
level | 1
compatible | yes
An existing rule for `check_ewon` without the mandatory key `device` would result in an exception
`KeyError (device)`.
This change makes the check function use a default, if `device` is not set.
[//]: # (werk v2)
# check_ewon: ValueError (incomplete format)
key | value
---------- | ---
date | 2024-08-06T07:52:50+00:00
version | 2.3.0p13
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Formatting a value with unit `%` would result in an invalid format-string making `check_ewon`
crash with an exception `ValueError (incomplete format)`.
This change makes `check_ewon` use f-formatting instead of `%`-formatting.
[//]: # (werk v2)
# Synthetic Monitoring: Avoid crash in scheduler (client side) during RCC setup
key | value
---------- | ---
date | 2024-08-06T05:54:33+00:00
version | 2.3.0p13
class | fix
edition | cee
component | checks
level | 1
compatible | yes
In one specific scenario, the Robotmk scheduler crashed during the RCC setup step. This happened if
if all plans using RCC were configured to run under a specific user instead of under the system
user.
Users have to update the agent on affected hosts to benefit from this werk.
[//]: # (werk v2)
# omd update: Log "Verifying site configuration"
key | value
---------- | ---
date | 2024-08-05T08:59:03+00:00
version | 2.3.0p12
class | fix
edition | cre
component | omd
level | 1
compatible | yes
If a user runs `omd update`, then the output is written to both `$OMD_ROOT/var/log/update.log` and
stdout. However, the output of site configuration verification
<a href="https://checkmk.com/werk/16408"> Werk #16408</a> was missing. This has been fixed.
[//]: # (werk v2)
# mk_informix: Follow up for Werk 16198
key | value
---------- | ---
date | 2024-07-26T07:18:38+00:00
version | 2.3.0p12
class | security
edition | cre
component | checks
level | 1
compatible | yes
[Werk #16198](https://checkmk.com/werk/16198) addressed potential priviledge escalation by the agent plugin `mk_informix`.
However, a few callsites to the binaries `dbaccess` and `onstat` where missing the safe execution.
Those binaries are now also called in a safe way.
<em>Vulnerability Management</em>:
We have rated the issue with a CVSS Score of 5.2 (Medium) with the following CVSS vector: <code>CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:H/SI:H/SA:H</code> and assigned CVE <code>CVE-2024-28829</code>.