#12163 Fedora Server VM Image Elevation to Distribution Media
Closed: Invalid 7 months ago by humaton. Opened 7 months ago by blackwell.

  • Describe the issue
    The Fedora Server Working group is looking to elevate the current Fedora Server VM Image to be a full distribution media that will be able hold a release due to any blockers similar to the ISO Images.

  • When do you need this? (YYYY/MM/DD)
    Before Fedora 41 but flexible

  • When is this no longer needed or useful? (YYYY/MM/DD)
    Will always be useful

  • If we cannot complete your request, what is the impact?
    Fedora Server VM Image will continue to be released without possibility of blocking due to issues similar to 40 release of Fedora Server VM image. Snippet from list where this request is originating.

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.

https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/4SNCGK7RKRDYGZM5P27GORXNLORO3ZE6/

Please let me know what the qualifications are to enable this or what requirements this type of request has.


Also, let me know if the terminology needs to be corrected here. Thanks!

This has to be proposed as a Change and go through FESCo, as documented at https://docs.fedoraproject.org/en-US/releases/f40/blocking/ : "This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo."

Metadata Update from @jnsamyak:
- Issue tagged with: meeting

7 months ago

Metadata Update from @humaton:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

7 months ago

Log in to comment on this ticket.

Metadata