Comment 5 for bug 1988942

@Sofia: I'm from the same team as Diko; I'll try to add some context here.

As far as I can tell, this is simply a matter of a metadata field, simplestreams_metadata, being longer than supported by the API in question.

We leverage simplestreams to automatically synchronize images from external repositories (e.g. http://cloud-images.ubuntu.com/releases/) into glance. Looking at it's code, it's simply using the create/upload/update methods of glanceclient.Client.images to create/update images in glance.

I see images created by simplestreams which clearly have this field exceeding 255 characters. And I see we can create instances or volumes with this image passed in via the --image field, and the instances/volumes are created without error, and the simplestreams_metadata field appears to be copied over without a problem.

Honestly, I'm not exactly sure what action is taking place in the log files uploaded by Diko that is triggering this, since the above does work fine.

However, if I run "openstack volume set --image-property simplestreams_metadata='<blob with over 255 characters>'" - even if I try to set the exact same property which is already set - I do get the same error. So, that seems inconsistent that we can create servers/volumes against an image with a larger field like this, but we can't set the property directly.

I've reproduced this issue using cinder-api version 2:14.2.1-0ubuntu1~cloud0 from the bionic-updates/stein/main pocket of the ubuntu cloud archive, but based upon looking at the sources in the master branch, I believe this bug still exists in the trunk.

Hope this helps.

Best Regards,
Paul Goins