Attempting to upload an image to a non-queued image appears to succeed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance Client |
Fix Released
|
Medium
|
Louis Taylor |
Bug Description
Steps to reproduce:
Create an image and upload data:
$ glance image-create --name non-queued --disk-format qcow2 --container-format bare --file some_image.img
Status of the image should now be 'active'. Now any attempts to upload different data will apparently succeed:
$ glance --debug image-update --file different_image.img <image-uuid>
+------
| Property | Value |
+------
| checksum | 4eada48c2843d2a
| container_format | bare |
| created_at | 2014-11-21T16:56:14 |
| deleted | False |
| deleted_at | None |
| disk_format | qcow2 |
| id | d50b0236-
| is_public | False |
| min_disk | 0 |
| min_ram | 0 |
| name | non-queued |
| owner | 07389013e3224e1
| protected | False |
| size | 25165824 |
| status | active |
| updated_at | 2014-11-21T17:04:57 |
| virtual_size | None |
+------
In actual fact, updating the image data of a non-queued image is not allowed and the new image data is silently stripped away from the request by the client before it is sent to the glance server. The fact that this operation has not succeeded should be communicated to the user.
Changed in python-glanceclient: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in python-glanceclient: | |
assignee: | nobody → Louis Taylor (kragniz) |
Changed in python-glanceclient: | |
milestone: | none → v0.16.0 |
Changed in python-glanceclient: | |
milestone: | v0.16.0 → v.16.1 |
Changed in python-glanceclient: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/136520
Review: https:/