[GH-ISSUE #220] Possibility to make "501 Not Implemented" silent, or propagate the error #124

New issue

Open

opened 2026-02-27 15:46:33 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 15:46:33 +03:00

Owner

Originally created by @grinapo on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/220

I am using prometheus-pve-exporter which in turn uses proxmoxer.

I am not sure who should be the target of my sorrow, but it dies on calling newish proxmox features (in this case /cluster/backup-info/not-backed-up) on and oldish proxmox. Gets 501, chokes on it.

I understand that this is handled "peroperly", but as far as a cursory look on the code goes it's not easy to call it (from pve-exporter) and handle the error, since the error doesn't get propagated.

My horrible solution was in core.py (147)

        if resp.status_code >= 400:
            return []
            …

but it's obviously a band-aid and not a solution (gives back empty iterable content, but uhh).

I'm not sure what the right solution would be, apart from possibility to actually propagate back the error instead of crashing.

Originally created by @grinapo on GitHub (Feb 17, 2026). Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/220 I am using `prometheus-pve-exporter` which in turn uses `proxmoxer`. I am not sure who should be the target of my sorrow, but it dies on calling newish proxmox features (in this case `/cluster/backup-info/not-backed-up`) on and oldish proxmox. Gets 501, chokes on it. I understand that this is handled "peroperly", but as far as a cursory look on the code goes it's not easy to call it (from pve-exporter) and handle the error, since the error doesn't get propagated. My horrible solution was in `core.py (147)` ```python if resp.status_code >= 400: return [] … ``` but it's obviously a band-aid and not a solution (gives back empty iterable content, but uhh). I'm not sure what the right solution would be, apart from possibility to actually propagate back the error instead of crashing.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/proxmoxer#124

No description provided.

Rows
Columns