Add error handling for maximum length of values
Bug #1406457 reported by
Adrian Otto
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Magnum |
Triaged
|
Wishlist
|
rajiv | ||
Bug Description
Add graceful error handling to politely decline to set a value, such as a pod label or image name that would cause the value to exceed the maximum configured length. Make the maximum configured length settable in the magnum configuration file. Allow different maximum lengths to be applied to different fields of each object. Use sensible defaults for these values that are known to work with a standard MySQL backing store.
Example of code needing this work applied:
https:/
| Changed in magnum: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| Changed in magnum: | |
| assignee: | nobody → Madhuri Kumari (madhuri-rai07) |
| description: | updated |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to magnum (master) | #1 |
| Changed in magnum: | |
| milestone: | none → mitaka-1 |
Revision history for this message
| Murali Allada (murali-allada) wrote | #2 |
| Changed in magnum: | |
| assignee: | Madhuri Kumari (madhuri-rai07) → nobody |
| Changed in magnum: | |
| assignee: | nobody → rajiv (rajiv-kumar) |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 88fd313abd6f391
Author: Tom Cammann <email address hidden>
Date: Fri May 1 15:56:46 2015 +0100
Add string length validation to names in APIs
Add string length validation bays, bay models and containers.
Change-Id: I50f39e6416bda1
Partial-Bug: 1406457