yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #27643
[Bug 1418061] Re: Images: 256 character limit isn't accurate for create image
Just adding to glance team for evaluation since the error is reported
out of the service response to horizon.
** Also affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1418061
Title:
Images: 256 character limit isn't accurate for create image
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Status in OpenStack Dashboard (Horizon):
In Progress
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1418061/+subscriptions
References