Currently, our VM distribution image is not a fully-fledged distribution medium like our iso media. It is merely a "nice to have“. This means, for example, that even a serious bug cannot become a "release blocker", as an iso file could. Fedora then launches a new release with a (on purpose) faulty Server VM image. This is already the case with release 40. Our VM image still contains the LVM error, which happens to be not immediately noticeable in a standard VM creation. And for the SBC image, the error will be corrected, although we do not currently know how. This no longer fits into today's world, where virtual machines are a common working model. To rectify this, we need to achieve a corresponding qualification with FESCo.
See on mailing list: Elevating Fedora Server VM distribution image
Metadata Update from @pboy: - Issue tagged with: meeting
From Jasons remarks on meeting:
for some context here is a similar proposal that has been announced for Fedora KDE AArch64 https://fedoraproject.org/wiki/Changes/Fedora_KDE_AArch64_ReleaseBlocker
here is the page for this effort ATM https://fedoraproject.org/wiki/Changes/FedoraServerReleaseBlockingDeliverable
If there is not preference on the images I can just request them all and see if we get pushback. I just don't have a good picture of what our current QA group is for Server so hopefully we would have resources to support the testing.
Request those specific images be marked for release-blocking deliverables https://docs.fedoraproject.org/en-US/releases/f40/blocking/
@pboy If you have time, can you take a look at the changes on https://fedoraproject.org/wiki/Changes/FedoraServerReleaseBlockingDeliverable and also advise on what we should put in the How to Test section if you have any ideas?
Metadata Update from @pboy: - Issue untagged with: meeting
Log in to comment on this ticket.