Today I was looking at the mirror repository for Hyperscale images, and I noticed that the AWS EC2 image we made in May is not there. Is something filtering that out?
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: cbs, low-trouble, medium-gain
I had a quick look and I see these builds tagged :
CentOS-Stream-Hyperscale-Spin-AWSEC2-9-0.n.202405071500 hyperscale9s-images-experimental-release ngompa CentOS-Stream-Hyperscale-Spin-GNOME-Live-9-0.n.202405071540 hyperscale9s-images-experimental-release ngompa CentOS-Stream-Hyperscale-Spin-KDE-Live-9-0.n.202405071540 hyperscale9s-images-experimental-release ngompa CentOS-Stream-Hyperscale-Spin-OpenStack-9-0.n.202405071500 hyperscale9s-images-experimental-release ngompa
But then I looked at that build and there is no iso/qcow2 image ?
https://cbs.centos.org/koji/buildinfo?buildID=53740
What's the kind of output kiwi was supposed to produce ? and even pushing further : you have tagged directly to -release something that wasn't even built ? :-)
It's amazing though, as https://cbs.centos.org/kojifiles/packages/CentOS-Stream-Hyperscale-Spin-AWSEC2/9/0.n.202405071500/data/logs/image/x86_64/image-root.x86_64.log clearly mentions :
[ INFO ]: 15:43:14 | --> disk_image: /builddir/result/image/CentOS-Stream-Hyperscale-Spin-AWSEC2.x86_64-9.raw
it should have raw.xz files at the end.
raw.xz
I see it compressed, yes .. Its just that releng process was only considering .iso, .qcow2 and .sha256 files. I added .raw.xz to the list, so can you just untag/retag your build ? it should then be processed and pushed out
Metadata Update from @arrfab: - Issue tagged with: feature-request
Just did it, waiting to see if it updates.
I see it was pushed correctly, so closing
Metadata Update from @arrfab: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.