min_ram and min_disk shouldn't ever be NULL

Bug #857711 reported by Brian Lamar on 2011-09-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
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:


A separate issue will be filed in Nova to have better error handing for this case.

Brian Lamar (blamar) on 2011-09-23
Changed in glance:
assignee: nobody → Brian Lamar (blamar)
Jay Pipes (jaypipes) on 2011-09-23
Changed in glance:
status: New → In Progress
importance: Undecided → Medium
milestone: none → essex-1

Reviewed: https://review.openstack.org/627
Committed: http://github.com/openstack/glance/commit/c81ebbcc5a985857e6c86c4b068c15585ddcad80
Submitter: Jenkins
Branch: master

 status fixcommitted

commit c81ebbcc5a985857e6c86c4b068c15585ddcad80
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: I0660b39b19a219e7999468839c0672e0c4911d88

Changed in glance:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2011-11-17
Changed in glance:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in glance:
milestone: essex-1 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers