Werk #20113: multipath: report vanished paths as CRIT again
| Component | Checks & agents | ||
| Title | multipath: report vanished paths as CRIT again | ||
| Date | Sep 22, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Incompatible - Manual interaction might be required | ||
| Checkmk versions & editions |
|
Since Werk #19280, the Multipath services on Linux hosts no longer noticed when paths
disappeared from the multipath -l output entirely. Service discovery had stopped recording
the number of paths, so the check compared the active paths against the paths it currently
saw. A device discovered with six paths that was down to three still reported OK with
"Paths active: 100.00%, 3 of 3 (expected: 3)".
Discovery now stores the number of paths again, and the check goes CRIT as soon as fewer
paths than that are active, as documented in the plugin's manual page. Paths that are still
listed but not in state "active" count as missing too, so a broken path on such a service is
CRIT by default again. Werk #19280 had made this WARN. If you prefer other thresholds,
use the ruleset Linux and Solaris Multipath Count.
Services discovered with an affected version show up as "changed" in the service discovery.
Accept them, or run a rediscovery, to restore the expected path count. Until then they keep
the previous behavior and only report WARN for paths in a non-active state.