Proxmox VE with tuenas storage plugin crashes because of unknown type

CMK version: 2.5.0p14
OS version: Debian Trixie

Error message:

Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)

[agent] Success, [special_proxmox_ve]     For further information visit Validation errors | Pydantic Docs - please submit a crash report! (Crash-ID: 0ed3790e-bfc0-11f1-8af5-000c29236ccc)(!!), [piggyback] Success (but no data found for this host), execution time 3.1 sec | execution_time=3.090
Agent exited with code 1: Found error for VM '109': "command 'qm shutdown 109 --skiplock --keepActive --timeout 600' failed: exit code 255"
Found error for VM '113': 'job failed with err -5 - Input/output error'
Found error for VM '113': 'job failed with err -5 - Input/output error'
Found error for VM '109': "command 'qm shutdown 109 --skiplock --keepActive --timeout 600' failed: exit code 255"
Traceback (most recent call last):
File "/omd/sites/oehl/lib/python3.13/site-packages/cmk/server_side_programs/v1_unstable/_crash_reporting.py", line 96, in wrapper
return func(*args, **kwargs)
File "/omd/sites/oehl/lib/python3.13/site-packages/cmk/plugins/proxmox_ve/special_agent/agent_proxmox_ve.py", line 534, in main
return agent_proxmox_ve_main(parse_arguments(sys.argv[1:]))
File "/omd/sites/oehl/lib/python3.13/site-packages/cmk/plugins/proxmox_ve/special_agent/agent_proxmox_ve.py", line 328, in agent_proxmox_ve_main
for name, content in _create_node_sections(
~~~~~~~~~~~~~~~~~~~~~^
node,
^^^^^
...<6 lines>...
data,
^^^^^
):
^
File "/omd/sites/oehl/lib/python3.13/site-packages/cmk/plugins/proxmox_ve/special_agent/agent_proxmox_ve.py", line 426, in _create_node_sections
SectionNodeStorages(
~~~~~~~~~~~~~~~~~~~^
node=node["node"],
^^^^^^^^^^^^^^^^^^
...<5 lines>...
storage_links=node_storage.get(node["node"], {}),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
).model_dump(),
^
File "/omd/sites/oehl/lib/python3.13/site-packages/pydantic/main.py", line 250, in init
validated_self = self.pydantic_validator.validate_python(data, self_instance=self)
pydantic_core._pydantic_core.ValidationError: 1 validation error for SectionNodeStorages
storages.3.plugintype
Input should be 'btrfs', 'cephfs', 'cifs', 'dir', 'esxi', 'iscsi', 'iscsidirect', 'lvm', 'lvmthin', 'nfs', 'pbs', 'rbd', 'zfs' or 'zfspool' [type=enum, input_value='truenas', input_type=str]
For further information visit Validation errors | Pydantic Docs
Failed: 1 validation error for SectionNodeStorages
storages.3.plugintype
Input should be 'btrfs', 'cephfs', 'cifs', 'dir', 'esxi', 'iscsi', 'iscsidirect', 'lvm', 'lvmthin', 'nfs', 'pbs', 'rbd', 'zfs' or 'zfspool' [type=enum, input_value='truenas', input_type=str]
For further information visit Validation errors | Pydantic Docs - please submit a crash report! (Crash-ID: 0ed3790e-bfc0-11f1-8af5-000c29236ccc)(!!)

This problem arises because there is a 3rd party storage plugin called proxmox-truenas installed and in use for all VMs.

root@pve ~ # pvesm status
TrueNAS [INFO] : Connected
TrueNAS [INFO] : Authenticated
TrueNAS [INFO] : Version: TrueNAS-25.10.7
Name                Type     Status     Total (KiB)      Used (KiB) Available (KiB)        %
local                dir     active        20466256         8038060        11363236   39.27%
...
pbs                  pbs     active      7523948544      2864119808      4659828736   38.07%
truenas          truenas     active      5344140971      1181819866      4162321104   22.11%
....

I should also add that i will probably move to the plugin truenas-proxmox-plugin if it enters a stable state (currently still in the testing phase) as the other will stop being maintained if it’s a working and stable alternative. But i haven’t yet looked at it closer so no idea if that would not be happening with it…

Anyhow, maybe the walkdown through the storages / vm-storages could not break completly if the type is not known?

EDIT: fwiw, i’m currently playing around with a truenas-27RC and the official truenas-proxmox-plugin. Here the type is as followed for either iscsi and nvme backend so i’m guessing this will end up the same way. As this system is not accessible from any checkmk host at the moment i can’t say for sure tho.

root@pve ~ # pvesm status
Name                 Type     Status     Total (KiB)      Used (KiB) Available (KiB)        %
local                 dir     active        17887232         7505960        10381272   41.96%
truenas-iscsi  truenasplugin     active        44909036         6048012        38861024   13.47%
truenas-nvme   truenasplugin     active        31457280              96        31457184    0.00%
truenastests3         pbs     active        17887232         7505960        10381272   41.96%

i guess this was fixed as i can’t seem to reproduce the problem anymore \o/.

This is also fixed in my proxmox_ve agent plugin. @crpb: Thanks for pointing that out to me.