Closed markus-hentsch closed 7 months ago
Apparently, we expect a dash where there's a space: ...image v1.26...
should be ...image-v1.26...
@berendt I don't recall how we arrived at the name scheme, but I presume I had a look at some existing image. Has anything changed about the naming?
Thanks everyone. In my opinion, this is not a problem with the image manager, but a bug in the namescheme. As pointed out by @garloff in the Matrix channel, the space character is what the SCS image metadata standard suggests: https://docs.scs.community/standards/scs-0102-v1-image-metadata#naming So I will file a bug issue in the standards repo and fix it there.
EDIT: The bug issue I promised. Funny that its number (viewed as a decimal string) is a permutation of this issue's number!
The current implementation of assembling image names^1 in the openstack-image-manager puts a space character between name and version for non-
multi
images.This seems in conflict with the image naming scheme currently mandated by SCS for the "ubuntu-capi-image"^2 where a hyphen is expected between name and version.
Consider the following example
images.yaml
as input (content shortened):This leads to:
... and does not pass the SCS conformance check^3 as it fails to recognize the "ubuntu-capi-image":