Werk #20113: multipath: detect vanished paths again
| Component | Checks & agents | ||||||
| Title | multipath: detect vanished paths 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. That werk removed the number of paths
that service discovery had recorded for each device, 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 records the number of paths again. Without a rule, the check compares the
active paths against that number and goes WARN when fewer are active, as Werk #19280
intended. It also goes WARN when more paths than recorded show up, which means a
rediscovery is due. The ruleset Linux and Solaris Multipath Count keeps its meaning:
an expected number of active paths is CRIT when undercut, and percentage levels work as
before.
Services discovered with an affected version show up as "changed" in the service discovery. Accept them, or run a rediscovery, to record the expected path count. Until then they keep the previous behavior and only notice paths that are listed in a non-active state.