Unsupported type 'drbd'

LINBIT SDS Integrations Proxmox VE
1

DRBD is working fine here on Proxmox as long as I just do stuff such as creating VMs, migrating them manually.

However, when Proxmox HA manager tries to do something with the VMs, I get messages such as

Dec 11 13:21:21 node1 pve-ha-lrm[2704500]: file /etc/pve/storage.cfg line 28 (skip section 'poolname'): unsupported type 'drbd'
Dec 11 13:21:21 node1 pve-ha-lrm[2704501]: file /etc/pve/storage.cfg line 28 (skip section 'poolname'): unsupported type 'drbd'
Dec 11 13:21:21 node1 pve-ha-lrm[2704504]: start VM 201: UPID:node1:00294478:021D36DF:675983C1:qmstart:201:root@pam:
[...]
Dec 11 13:21:22 node1 pve-ha-lrm[2704504]: storage 'poolname' does not exist
Dec 11 13:21:22 node1 pve-ha-lrm[2704501]: <root@pam> end task UPID:node1:00294479:021D36DF:675983C1:qmstart:202:root@pam: storage 'poolname' does not exist
Dec 11 13:21:22 node1 pve-ha-lrm[2704501]: unable to start service vm:202

and then HA goes into an error state.

Looking on the internets, there’s a topic on the proxmox forums from ages ago, where DRBD’s integration plugin on the poster’s machine was too old and he could fix it by updating. That shouldn’t be the case here - the whole thing was installed today.

The message “file /etc/pve/storage.cfg line 28 (skip section ‘poolname’): unsupported type ‘drbd’” comes up a bunch of times, but it seems to be just a warning, so everything still works.
However the “storage ‘poolname’ does not exist” shows up as an error, it causes HA to go into an error state.

Is this something others have or have had too?

storage.cfg looks kinda like this:

drbd: poolname
   content images,rootdir
   controller ip1,ip2
   resourcegroup rg_name
1 Like
2

I saw such issues before, but the bad news is that I don’t really have a solution. Sometimes it looks like the PVE parser gets confused for no obvious reason. Then one can remove the section, add it again, restart the pvedaemon.service. Sometimes this helps, sometimes it does not. In a recent case where we tried everything, eventually a reboot of that box solved the issue.

It looks like the parser is easy to confuse and that then the state is somewhere cached/kept. While on the other hand usually changes to storage.cfg “show up” immediately.

tl;tr: I saw that as well, I have no idea why the parser/PVE sometimes gets confused, and I also don’t really know how to fix it. From my experience: if it works, then it works, this usually happens when adding a new storage definition.

2 Likes
3

Interesting - so you think it’s a problem within Proxmox, where the parser doesn’t accept something it should accept?

I mean I didn’t look through the Proxmox code yet, but if you think that’s what it is, and if it’s time well invested, then I might …

1 Like