Image set --volume does not work / cinder upload-to-image

Bug #1505236 reported by Niall Bunting
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-cinderclient
Invalid
Undecided
Unassigned
python-openstackclient
Invalid
Undecided
Niall Bunting

Bug Description

Overview:
When trying to do an image set with the --volume its seems to not do anything.

This is because the cinder command: upload-to-image does not seem to work with v2 in glance.

Steps to reproduce:
openstack image set ed573fb1-3ebd-46e7-887b-5f6aed5a9c97 --volume 83f26ea5-d7b5-42cd-8bd9-28de72c65c01

Output:
It actually fails with the problem that update does not take the keyword volume. If you try to fix that problem it turns out that this does nothing anyway.
Network traffic: http://paste.openstack.org/show/476022/

Expected:
Should update the image with the given properties and update to use the volume.

Changed in python-openstackclient:
assignee: nobody → Niall Bunting (niall-bunting)
Revision history for this message
Niall Bunting (niall-bunting) wrote :

It seems this is a problem with the cinder upload-to-image. As it seems to just create a different image with the same name, rather than changing the actual image.

Revision history for this message
Steve Martinelli (stevemar) wrote :
summary: - Image set --volume does not work
+ Image set --volume does not work / cinder upload-to-image
description: updated
Revision history for this message
Nate Potter (ntpttr) wrote :

I could be understanding your description of this bug incorrectly, but I'm not sure how this means that the cinderclient's upload_to_image function isn't working. That function is supposed to take a volume and upload it to glance as an image - volume is a positional argument in that function, not an optional one, since it needs to know which volume to upload. So really there should be no image passed in for it to change, what do you mean by "create a different image with the same name, rather than changing the actual image"?

Revision history for this message
Niall Bunting (niall-bunting) wrote :

@Nate Yeah, I see now. On a different note, I think the implementation by cinder needs to be upgraded to v2.

Changed in python-cinderclient:
status: New → Invalid
Changed in python-openstackclient:
status: New → Invalid
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.