dustymabe added a new comment to an issue you are following:
``
Could you pleas be explicit? Exactly what is the breakage here, how
do I recreate it?
Of course. There are several that I can think of:
- changing the image type in the middle of a release is problematic. We release atomic
host every two weeks and will continue to do so for f29 until Fedora 29 EOL
- a UEFI only cloud image means we [won't be in the largest cloud that exists
(
AWS)](https://docs.aws.amazon.com/vm-import/latest/userguide/vmie_prereqs...)
- *UEFI/EFI boot partitions are supported only for Windows boot volumes with VHDX as
the image format. Otherwise, a VM's boot volume must use Master Boot Record (MBR)
partitions.*
I believe we need to make UEFI vs non-UEFI configurable and probably need to release both
types of images for x86_64.
I feel this has actually exposed an anaconda bug.
AFAIK anaconda only queues decides on UEFI vs non-UEFI based on how the VM it is
installing into was booted. I don't think there is an option for this. If you find one
I'd be very happy to use it!
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8197