Feature #962
Improve error messages
| Status: | Closed | Start date: | 11/04/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 3.4 | |||
| Resolution: | fixed | Pull request: |
Description
Some error messages are too vague, and could be improved including useful information.
For instance, the error "Could not get virtual network for VM." doesn't say which network failed (a VM can have several NIC attributes), and it doesn't say the reason: the network doesn't exist, it doesn't have any more free leases, or the requested IP is not part of that network.
"Could not get disk image for VM." has the same problem.
"Can not delete image" could inform that images can't be deleted if they are in the used state.
History
#1
Updated by Cyril Rohr over 9 years ago
Carlos Martín wrote:
Some error messages are too vague, and could be improved including useful information.
For instance, the error "Could not get virtual network for VM." doesn't say which network failed (a VM can have several NIC attributes), and it doesn't say the reason: the network doesn't exist, it doesn't have any more free leases, or the requested IP is not part of that network.
+1. Most of the time it means that it can't get a lease. The error message is misleading. Could you improve it please?
Tested on ONE 3.0.0.
#2
Updated by Carlos Martín over 9 years ago
- Target version set to Release 3.4
#3
Updated by Ruben S. Montero over 9 years ago
- Status changed from New to Closed
- Resolution set to fixed
Some work done in this are. Closing this and we'll open additional issues if needed for specific components,