min_ram and min_disk shouldn't ever be NULL
Bug #857711 reported by
Brian Lamar
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Glance |
Fix Released
|
Medium
|
Brian Lamar | ||
Bug Description
Currently the 009 migration will set existing images to None, instead of 0. This is causing issues down the line and should be remedied. This is the root of the cause for this traceback in Nova:
http://
A separate issue will be filed in Nova to have better error handing for this case.
| Changed in glance: | |
| assignee: | nobody → Brian Lamar (blamar) |
| Changed in glance: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| milestone: | none → essex-1 |
Revision history for this message
| Openstack Gerrit (openstack-gerrit) wrote A change has been merged to openstack/glance | #1 |
| Changed in glance: | |
| status: | In Progress → Fix Committed |
| Changed in glance: | |
| status: | Fix Committed → Fix Released |
| Changed in glance: | |
| milestone: | essex-1 → 2012.1 |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
status fixcommitted
done
commit c81ebbcc5a98585
Author: Brian Lamar <email address hidden>
Date: Fri Sep 23 16:30:01 2011 -0400
Do not allow min_ram or min_disk properties to be NULL and if they are None, make sure to default to 0. Fixes bug 857711
Change-Id: I0660b39b19a219