Nullable fields default values are not part of the schema
Bug #1398313 reported by
Flavio Percoco
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Glance |
Fix Released
|
Medium
|
Flavio Percoco | ||
Bug Description
Some fields in the v2 that are nullable - disk_format and container_format, for example - don't have `None` as one of the possible values in their enum. This prevents the API from sending the value back to the client and the client library doesn't consider `None` as a valid value for the field.
| Changed in glance: | |
| assignee: | nobody → Flavio Percoco (flaper87) |
| Changed in glance: | |
| status: | New → In Progress |
| Changed in glance: | |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to glance (master) | #1 |
| Changed in glance: | |
| status: | In Progress → Fix Committed |
| Changed in glance: | |
| milestone: | none → kilo-1 |
| status: | Fix Committed → Fix Released |
| Changed in glance: | |
| milestone: | kilo-1 → 2015.1.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 8b3ca087b7d3bbc
Author: Flavio Percoco <email address hidden>
Date: Mon Dec 1 14:45:44 2014 +0100
Allow some fields to be None
Container, disk format and checksum - among other fields - are not
required parameters, therfore this patch allows them to be None.
This will allow the client to have attributes with value `None` and
it'll make it consistent across responses and with regards to the API.
NOTE: A follow-up patch will enable None values to be returned by the API.
Closes-bug: #1398313
Change-Id: I75da1e9309e0f7