Images: 256 character limit isn't accurate for create image
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Opinion
|
Undecided
|
Unassigned | ||
OpenStack Dashboard (Horizon) |
Fix Released
|
Undecided
|
Nikunj Aggarwal |
Bug Description
The 256 characters limit for Images doesn't seem quite accurate. If you try to set up a long name with special characters (less than 256 characters, but more than 256 bytes?) it fails.
A user reported:
1. Create a image and the name of the image should be more than 256 bytes. For example: を引き続きご使用になるお客様は
2. Horizon fails with a generic error.
But actually it is the same with e.g. just creating a new image (The error returned is the generic: "Unable to create new image. ")
We see this in the logs:
[Tue Jan 20 16:40:45.594430 2015] [:error] [pid 17230] Recoverable error: <html>
[Tue Jan 20 16:40:45.594454 2015] [:error] [pid 17230] <head>
[Tue Jan 20 16:40:45.594458 2015] [:error] [pid 17230] <title>400 Bad Request</title>
[Tue Jan 20 16:40:45.594460 2015] [:error] [pid 17230] </head>
[Tue Jan 20 16:40:45.594462 2015] [:error] [pid 17230] <body>
[Tue Jan 20 16:40:45.594465 2015] [:error] [pid 17230] <h1>400 Bad Request</h1>
[Tue Jan 20 16:40:45.594467 2015] [:error] [pid 17230] Image name too long: 405<br /><br />
[Tue Jan 20 16:40:45.594469 2015] [:error] [pid 17230]
[Tue Jan 20 16:40:45.594472 2015] [:error] [pid 17230] </body>
[Tue Jan 20 16:40:45.594474 2015] [:error] [pid 17230] </html> (HTTP 400)
So Glance does return a more meaningful error, that we should try to present to the user.
Changed in horizon: | |
assignee: | nobody → Nikunj Aggarwal (nikunj2512) |
Changed in horizon: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | kilo-3 → 2015.1.0 |
Changed in glance: | |
status: | New → Fix Committed |
status: | Fix Committed → Opinion |
Fix proposed to branch: master /review. openstack. org/152927
Review: https:/