Pulse/pkg/proxmox
rcourtman 7c895df1f3 Fix Proxmox 9.x VM status endpoint incompatibility
Proxmox VE 9.x removed support for the "full" parameter in the
/nodes/{node}/qemu/{vmid}/status/current endpoint. When Pulse sent
GetVMStatus() requests with ?full=1, Proxmox responded with:

  API error 400: {"errors":{"full":"property is not defined in schema..."}}

This caused the cluster client to mark ALL endpoints as unhealthy, which
cascaded into multiple failures:
- VM status checks failed
- Guest agent queries were blocked
- Filesystem data collection stopped working
- All Windows VMs showed disk:-1 (unknown) instead of actual disk usage

The fix removes the ?full=1 parameter since Proxmox 9.x returns all data
by default without needing this parameter. This maintains backward
compatibility with older Proxmox versions while fixing the issue in 9.x.

After this fix:
- Cluster endpoints are correctly marked as healthy
- Guest agent queries work properly
- Windows VMs report actual disk usage (e.g., 26% on C:\ drive)
- VM monitoring functions normally on Proxmox 9.x
2025-11-13 11:22:36 +00:00
..
ceph.go Fix settings security tab navigation 2025-10-11 23:29:47 +00:00
client.go Fix Proxmox 9.x VM status endpoint incompatibility 2025-11-13 11:22:36 +00:00
client_test.go Add replication monitoring plumbing and UI 2025-10-22 16:10:15 +00:00
cluster_client.go Fix Proxmox 9.x RRD parameter incompatibility causing cluster health issues 2025-11-08 12:06:08 +00:00
cluster_client_test.go security: complete Phase 1 sensor proxy hardening 2025-10-20 15:13:37 +00:00
replication.go Add replication monitoring plumbing and UI 2025-10-22 16:10:15 +00:00
zfs.go Fix false ZFS log/cache warnings 2025-10-14 20:57:43 +00:00
zfs_test.go Expand monitoring and discovery test coverage 2025-10-16 08:17:08 +00:00