Werk #19461: Fix Proxmox VE node allocation crash on missing CPU or memory capacity data
| Component | Checks & agents | ||||
| Title | Fix Proxmox VE node allocation crash on missing CPU or memory capacity data | ||||
| Date | May 6, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
Previously, the Proxmox VE CPU Allocation and Proxmox VE Memory Allocation services could crash with a KeyError when the Proxmox VE API did not include maxcpu or maxmem in the node status response — for example on offline nodes or nodes with incomplete API responses.
Both services now handle missing capacity data gracefully: if maxcpu or maxmem are absent from the node data, the allocation sections are not emitted and no service is discovered for that node.