openstack/glance
Code Issues Proposed changes
OpenStack Image Management (Glance)
6,094 Commits 11 Branches 55 Tags 130 MiB
Python 99.9%
2562da28c6
Go to file
Dinesh Bhor 2562da28c6 Fix 500 if user passes name with more than 80 characters 
Following apis are returning 500 error if user passes name with more
than 80 characters:
* md-tag-create
* md-tag-update
* md-object-create
* md-object-update
* md-property-create
* md-property-update

This happens because there is a discrepancy in db column length and
glance-api length check in schema validation. In database the 'name'
field for these API's is defined as of maximum 80 characters and in
schema it is defined as of maximum 255 characters. So if user passes
name with more than 80 characters and less than 255 characters
database fails to store that value and shouts with following error
which leads to 500 error to API user:

(pymysql.err.DataError) (1406, u"Data too long for column 'name' at
row 1")

Fixed this issue by changing the maximum allowed length for 'name'
from 255 to 80 in schema validation.

APIImpact
DocImpact
Closes-Bug: #1719252
Change-Id: I4ae67457c3e4f5a6bfc3c1db2d305a9b7587395f
2017-10-05 10:24:22 +05:30
api-ref/source Fix 500 if user passes name with more than 80 characters 2017-10-05 10:24:22 +05:30
doc/source Update image statuses doc for latest change 2017-09-25 16:16:38 +08:00
etc Add 'tasks_api_access' policy 2017-08-18 00:46:34 -04:00
glance Fix 500 if user passes name with more than 80 characters 2017-10-05 10:24:22 +05:30
httpd Add docs and sample configs for running glance with apache 2017-06-18 04:00:48 -04:00
rally-jobs Merge "Add 'vhdx' disk format." 2016-08-01 18:32:59 +00:00
releasenotes Fix 500 if user passes name with more than 80 characters 2017-10-05 10:24:22 +05:30
tools Prepare for using standard python tests 2017-02-03 20:11:48 +01:00
.coveragerc Update .coveragerc after the removal of openstack directory 2016-10-17 17:09:56 +05:30
.gitignore rearrange existing documentation to follow the new layout standard 2017-06-21 14:15:58 -04:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 11:02:16 -04:00
.mailmap Add a mailmap entry for myself 2014-02-11 12:00:44 +08:00
.testr.conf Allow specifying OS_TEST_PATH (to reduce tests ran) 2016-11-07 11:09:26 -08:00
babel.cfg Added first step of babel-based translations. 2012-02-28 02:00:37 -08:00
bandit.yaml Move bandit into pep8 2016-02-26 08:12:45 +01:00
CONTRIBUTING.rst Update the documention for doc migration 2017-08-02 07:22:46 +00:00
HACKING.rst Stop enforcing translations on logs 2017-05-31 11:35:53 +01:00
LICENSE Add a LICENSE file. 2012-01-03 10:14:01 -05:00
pylintrc Typo in pylintrc file 2015-03-25 11:21:16 +01:00
README.rst Remove team:diverse-affiliation from tags 2017-07-21 14:52:59 +01:00
requirements.txt Updated from global requirements 2017-09-26 15:45:52 +00:00
setup.cfg Merge "Update URL home-page in documents according to document migration" 2017-08-28 18:40:43 +00:00
setup.py Updated from global requirements 2017-03-04 01:43:26 +00:00
test-requirements.txt Updated from global requirements 2017-09-16 23:11:44 +00:00
tox.ini Clean up py35 env in tox.ini. 2017-05-09 22:54:59 +00:00

README.rst

Team and repository tags

The following tags have been asserted for the Glance project: "project:official", "tc:approved-release", "stable:follows-policy", "tc:starter-kit:compute", "vulnerability:managed", "assert:supports-upgrade", "assert:follows-standard-deprecation". Follow the link for an explanation of these tags.

Glance

Glance is a project that provides services and associated libraries to store, browse, share, distribute and manage bootable disk images, other data closely associated with initializing compute resources, and metadata definitions.

Use the following resources to learn more:

API

To learn how to use Glance's API, consult the documentation available online at:

Developers

For information on how to contribute to Glance, please see the contents of the CONTRIBUTING.rst in this repository.

Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.

Further developer focused documentation is available at:

Operators

To learn how to deploy and configure OpenStack Glance, consult the documentation available online at:

In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. You can raise bugs here:

Other Information

During each design summit, we agree on what the whole community wants to focus on for the upcoming release. You can see image service plans:

For more information about the Glance project please see: