BUG: 2.2 and levels for absolute free space & magic factor not working together

[carnold (Christian Arnold)]

CMK version: 2.2.0p5
OS version: Ubuntu 20.04

Error message:
The absolute free warn/crit levels of all my previously working rules don’t work anymore. Instead, the levels_low are getting applied.

This is how the parameters are getting applied without me changing the rule:

{'levels': (-10240, -7168), 'magic': 1.0, 'magic_normsize': 20, 'levels_low': (50.0, 60.0), 'show_levels': 'onmagic', 'inodes_levels': (10.0, 5.0), 'show_inodes': 'onlow', 'show_reserved': False, 'trend_range': 24, 'trend_perfdata': True, 'item_appearance': 'mountpoint', 'mountpoint_for_block_devices': 'volume_name'}

Previously I needed to set the magic factor to 1.0 so my absolute MB values for filesystem levels (regular and NetApp) to work while using magic for all other filesystems. This stopped working after updating to 2.2.0.

How am I supposed to set a simple level now while also using MF for everything else?

[carnold (Christian Arnold)]

Does nobody else use the magic factor as default and absolute levels for some filesystems?

[andreas-doehler (Andreas)]

I don’t use such a rule, but i can confirm that there is a bug inside the actual df check.
What i tested.
Generic rule - magic factor 0.6 and lower level if magic factor is used 80/90%

One rule with with absolute levels for one single mountpoint.
→ rule

result in check

warn/crit values are plainly wrong
as @carnold wrote these levels are the lower levels from the magic factor.

[lracic (Luka Racic)]

Hello @carnold,

As agreed in the SUP ticket, the Werk number for the fix is 15908. It should go live with 2.2.0p8.

KR,
Luka