API /api2/json/cluster/config/qdevice not working

[bas]

Hello,

API call "/api2/json/cluster/config/qdevice" does not work.

I get this response:

{
  "data": {
    
  }
}

When running it through the CLI "pvesh get /cluster/config/qdevice --output-format json-pretty" I get the correct output (I masked the IP):

{
   "Algorithm" : "Fifty-Fifty split",
   "Last poll call" : "2022-05-10T14:00:35 (cast vote)",
   "Model" : "Net",
   "QNetd host" : "***.***.***.***:5403",
   "State" : "Connected",
   "Tie-breaker" : "Node with lowest node ID"
}

We run PVE 5.15.30-3 community on all nodes.

Can this be fixed?

Regards,
Bas

 

[oguz]

hi,

We run PVE 5.15.30-3 community on all nodes.

this is pretty old and outdated version of PVE. you should probably think about upgrading your cluster [0] [1]

API call "/api2/json/cluster/config/qdevice" does not work.

how exactly are you making your API call?



[0]: https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
[1]: https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0

 

[bas]

Hello,

Sorry, that was the kernel:

proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)

We are making the API call from the browser with a root session open. But it also doesn't work with Postman with the authorization header with an API key.

Regards,
Bas

 

[oguz]

Sorry, that was the kernel:

oh okay

We are making the API call from the browser with a root session open. But it also doesn't work with Postman with the authorization header with an API key.

could you show us an example? (you can censor out the IP addresses and tokens)

do you also have the csrf token? [0]

[0]: https://pve.proxmox.com/wiki/Proxmox_VE_API#Example:_Get_a_New_Ticket_and_the_CSRF_Prevention_Token

 

[bas]

Hello,

I just go to the URL in a webbrowser in a session that's already authenticated in the web UI of Proxmox. All other API calls work fine, just this one doesn't return any data.

 

[sterzy]

Hi,

yes the issue seems related to write permissions on the qdevice socket (/var/run/corosync-qdevice/corosync-qdevice.sock). The API runs under the user www-data for that endpoint, which does not have write permissions on the socket. pvesh runs under root instead (at least I am assuming you invoked it as root). We'll update you here once this is resolved

 

[sterzy]

Hi,

small update, a patch is available on the mailing list [1]. You could apply it locally to test whether this fixes your issue.

[1]: https://lists.proxmox.com/pipermail/pve-devel/2022-May/052975.html

 

[sterzy]

The patch [1] has been applied and will be included in the next update!

[1]: https://git.proxmox.com/?p=pve-cluster.git;a=commit;h=665156658d8f492406ab4272b461d7ed9d6716d2

 

[bas]

The patch [1] has been applied and will be included in the next update!

[1]: https://git.proxmox.com/?p=pve-cluster.git;a=commit;h=665156658d8f492406ab4272b461d7ed9d6716d2

Thanks! I'll try again once the update is released and installed.