[pve-devel] Feature Request: Enhancing Error Messaging

[Rovshan Pashayev]

Hello Fabian,

Example:
If we attempt to start VM with problematic storages from WebUI, we might see following error (example):
https://i.ibb.co/Lx5QjCg/image-2.png

But if we attempt start action via SSH request we get both output in the one line (example):
WARN: no efidisk configured! Using temporary efivars disk. storage 'NFS_pve-storage' does not exist

Which causes confusion, during differentiating errors.

________________________________________
From: Fabian Grünbichler <f.gruenbichler at proxmox.com>
Sent: Tuesday, July 2, 2024 14:19
To: Proxmox VE development discussion <pve-devel at lists.proxmox.com>
Cc: Rovshan Pashayev <Rovshan.Pashayev at veeam.com>
Subject: Re: [pve-devel] Feature Request: Enhancing Error Messaging


> Rovshan Pashayev via pve-devel <pve-devel at lists.proxmox.com> hat am 02.07.2024 12:50 CEST geschrieben:

> We kindly request the implementation of enhanced error messaging. Currently, all errors and failures are combined into a single string, making it difficult to identify and address specific issues.

which errors? for which actions/API endpoints/..?

> Please consider introducing error codes or a similar mechanism to provide a structured format for error reporting. This would improve the user experience and expedite troubleshooting during third-party backup processes.

we try to keep the errors meaningful and easy to understand. if you have concrete examples that could benefit from more detail or changed contents, feel free to file issues at https://bugzilla.proxmox.com/

we are not planning to add error codes (like E1234) to our error messages at the moment - in our experience, those don't provide much added benefit at the level of interaction PVE usually provides.

structured error types can make sense for low level interfaces (where callers might decide on a course of action based on the error, like retrying). note that we do differentiate between lacking permissions, bad parameters and other errors also on the API level.