Werk #22476: pse_poe: report an unknown operational status instead of crashing
| Component | Checks & agents | ||||||
| Title | pse_poe: report an unknown operational status instead of crashing | ||||||
| Date | Sep 22, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
If a power sourcing device reported an operational status other than on, off or
faulty, Checkmk could not read the pse_poe section at all. It failed with
ValueError: <n> is not a valid PoeStatus, produced a crash report on every
check cycle, and all POE services of that switch stopped being updated --
not just the port with the odd status.
The check already knew how to report such a value, but the section was rejected
before it got there. An unknown status now reaches the check, which reports
UNKNOWN and quotes the value the device sent, for example
Device returned faulty data: nominal power: 50, power consumption: 20,
operational status: 0. The other ports of the switch are monitored as before.