dustymabe reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The Atomic Host cloud images output by the updates pungi composes (kicked off by bodhi)
started producing images that only boot in UEFI mode. This happens if the VM anaconda was
run in was started in UEFI mode. Something changed that caused this to start happening.
The images from
[
20190227.0](https://kojipkgs.fedoraproject.org/compose/updates/Fedora-29-...
are fine while the images from
[
20190228.0](https://kojipkgs.fedoraproject.org/compose/updates/Fedora-29-...
show the problem. There are no package differences between these images.
The difference is that if you look at the oz logs from the tasks
[
20190227.0](https://koji.fedoraproject.org/koji/taskinfo?taskID=33075126)
[
20190228.0](https://koji.fedoraproject.org/koji/taskinfo?taskID=33107624) you can see
that one is choosing BIOS boot and one is choosing UEFI boot:
```
:02:12,338 INFO anaconda:anaconda: bootloader: bootloader GRUB2 on X86 platform
```
vs
```
:25:31,273 INFO anaconda:anaconda: bootloader: bootloader EFIGRUB on EFI platform
```
You can also see in the tdl files the `<nvram
template="/usr/share/OVMF/OVMF_VARS.fd"/>` which is a sign of booting via
UEFI.
This change is causing breakage for Atomic Host release artifacts and is preventing us
from releasing the next two week release of Atomic Host.
* When do you need this? (YYYY/MM/DD)
A fix ASAP would be nice. Ideally we would be able to release tomorrow.
* When is this no longer needed or useful? (YYYY/MM/DD)
N/A
* If we cannot complete your request, what is the impact?
No more releases of Atomic Host.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8197