Image Type is Erroneously Required

Bug #724654 reported by Rick Harris
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Fix Released
Medium
Rick Harris

Bug Description

`image_type` is going away, but until the disk_format and container format stuff merge we have a bit of a problem.

This patch https://code.launchpad.net/~jaypipes/glance/bug704854/+merge/50773 introduced a requirement on image.`type` to always be present.

However, when we take a snapshot from nova, however, we don't know upfront (in the reserve phase) which format the underlying virt-layer is going to use (raw vs vhd).

So, we need to be able to queue an image without a `type` and then add one before it goes into `saving`.

Image.`type` is nullable in the DB, and this pattern was working up until this patch, so I don't think it's a problem to revert back to old behavior with respect to image type. The rest of the patch seems fine.

Related branches

Changed in glance:
assignee: nobody → Rick Harris (rconradharris)
importance: Undecided → Medium
status: New → In Progress
Changed in glance:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in glance:
milestone: none → 2011.2
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.