Comment 7 for bug 1419823

Revision history for this message
Clayton O'Neill (clayton-oneill) wrote :

When ran into this while doing test upgrades to Kilo. After doing the upgrade, we were no longer able to boot some images, and turned out to be because we had several images with NULL description fields. I was able to validate that the glance v1 api still allows creating images of this type with the following command:

    glance image-create --name cirros_test --disk-format qcow2 --container-format bare --file cirros-0.3.4-x86_64-disk.img --is-public True --is-protected True --progress --property description=

At this point we're trying to figure out how to work around this issue. Right now it's possible for clients to use the v1 api to create images they cannot boot, and the failure mode from nova just looks like it cannot find a node to schedule on. That's pretty opaque to end users.