Cannot add architecture property when it does not exist

Bug #1334322 reported by Justin Pomeroy
This bug affects 2 people
Affects Status Importance Assigned to Milestone
In Progress
Kent Wang

Bug Description

I have an environment set up using the latest devstack. One of the images provided by devstack (cirros-0.3.2-x86_64-uec) contains two custom properties: kernel_id and ramdisk_id. I tried to use the glance v2 API to add the architecture property and this resulted in a 409 Conflict error. It seems the behavior of glance in this case is to try to actually replace this property instead of add it, and that results in the conflict since the property does not exist.

Revision history for this message
Kent Wang ( wrote :

Hi I wasn't able to reproduce your bug. Can you provide more detailed steps?
Also the docs here talk about the 409 conflict errors for properties:
Looks like it may have to do with the current image status

Revision history for this message
Justin Pomeroy (jpomero) wrote :

This might be specific to the v2 API, or caused by using the v1 API to create the image and the v2 API to update it. These are the steps to recreate:

1) Import an image into glance, do not specify the architecture property so that it does not exist.
2) Run the following command to add the architecture property:
     glance --os-image-api-version 2 image-update --property architecture=x86_64 <image-id>

This will result in 409 Conflict.

Kent Wang (
Changed in glance:
assignee: nobody → Kent Wang (
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to glance (master)

Fix proposed to branch: master

Changed in glance:
status: New → In Progress
Revision history for this message
Zhi Yan Liu (lzy-dev) wrote :

Mark this as a duplication to bug/1371559 due to that one see/fix this issue from a more common way. Thanks report this issue.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on glance (master)

Change abandoned by Zhi Yan Liu (<email address hidden>) on branch: master

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.