Comment 5 for bug 1220104

This bugzilla has several weak points in the tacking workflow. Currently nobody has assigned. is still marked as Fix Released without poiting the milestone or the patch itself

At least on old icehouse the result of the reported command is unfortunate, as it doesn't provide enough feedback to the user about what's happening.

However, the real motivation of the "misfunctioning" command is that images are immutable resources and once you create them, you can't modify them.

this changes in v2 a bit since you can now upload the image yourself and add more remote locations, although not recommended. Users have always be encouraged to treat images as unique, immutable resources.

A workaround for this may be to use image names instead of image ids. Whenever an image wants to be updated, re-use the image name and delete/rename the previous one.

Is this something other people are willing to do?

At that time y no recommended way to do this other than update the images by creating new ones. One reason is that uploading a new image may require changing the checksum (which some users rely on), the size of the image, etc. All these can lead to inconsistencies in user environments and across the cloud, hence images are immutable.

Let's hear other opinions.