nova boot error messages are uninformative
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Invalid
|
Low
|
Unassigned | ||
Bug Description
Description:
1. Create a VM using following nova boot command:
nova boot --image 117 --flavor 100 --key_name onekey --user_data testfile1 --meta "roshan=anvekar" --file /home/ubuntu/
Server Error, please try again later. (HTTP 500)
------ As per my project setting I had allocated the resources so that both meta and file file size bytes should go wrong. But the Server was not able to handle the error and dint give any meaningful info too.
2. The error is very vague when we try to create a VM with multiple parameters and some of the parameters are wrongly given.
3. Feel that there is no proper concatenation of user error messages and also it fails to throw proper messages when multiple parameters are not given properly.
4. The user finds it very difficult to analyze as what went wrong.
| Changed in nova: | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| tags: | added: python-novaclient |
| Brian Waldon (bcwaldon) wrote | #1 |
| Changed in nova: | |
| status: | Confirmed → Invalid |
Here's what happens when I send a metadata key/value that is too large:
$ nova boot --image=
Quota exceeded for 686f1612aa7d456
And here's what happens with an oversized file:
$nova boot --image=
Personality file content too long (HTTP 413)
As overLimit failures are now being correctly handled, I'm going to mark this as invalid. Please reopen it if you feel otherwise.