Werk #10840: Fix evaluation of time specific parameters if default parameters are tuple based
| Component | Checks & agents | ||||||
| Title | Fix evaluation of time specific parameters if default parameters are tuple based | ||||||
| Date | Mar 18, 2020 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
Old tuple based parameters may look like
NAME_default_levels = (90.0, 95.0)
In this case if time specific parameters are additionally configured and the check is executed outside of this time period then the evaluation of these parameters crashed
TypeError: cannot convert dictionary update sequence element #0 to a sequence
Now we simply ignore the (old) tuple-based parameters. A rule with a timespecifc parameter settings always has an implicit default parameter set, even if no timeperiod matches.