Comment 5 for bug 1419823

glance v1 api allows image properties to be set as null and v2 defines a schema that doesn't allow null properties. It is so easy to run into this problem when booting instances with a hypervisor driver that leverages image locations from v2 but the image has null properties set through v1 api.

Adding to Kamil's, we can choose not to send null valued properties in response via v2 api.