Bug 2185883

Summary:	Register EC2 Cloud Images with uefi-preferred AMI flag
Product:	[Fedora] Fedora	Reporter:	Ben Cotton <bcotton>
Component:	Changes Tracking	Assignee:	Stewart Smith <trawets>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	39	CC:	amoloney, awilliam, davdunc, mvadkert, thrcka, trawets
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-14 18:57:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2158243

Description Ben Cotton 2023-04-11 13:52:04 UTC

This is a tracking bug for Change: Register EC2 Cloud Images with uefi-preferred AMI flag
For more details, see: https://fedoraproject.org/wiki/Changes/CloudEC2UEFIPreferred

A new feature of EC2 is to be able to register AMIs with a boot mode of uefi-preferred rather than picking one of bios or uefi. In EC2, aarch64 has always been UEFI, while x86-64 started out as BIOS only and some instance types have recently begun to support booting in UEFI mode. Previously, an AMI had to pick if it was UEFI or BIOS. With uefi-preferred it allows an AMI to launch with whatever firmware stack is available for the instance type, preferring UEFI when UEFI is an option.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Adam Williamson 2023-08-22 23:01:07 UTC

Unless I'm missing something, I don't think this has been done. Best as I can tell, it would happen in the infra ansible fedimg role - https://pagure.io/fedora-infra/ansible/blob/main/f/roles/fedimg - but I don't see any indication that it *has* happened.

If I'm right, as we're past the Beta freeze, this is very late and at risk for F39.

Comment 2 Adam Williamson 2023-09-21 19:20:49 UTC

I still see no indication this has been done. It should probably be postponed to F40 at this point, unless I'm wrong.

David, do you know what's going on here?

Comment 3 Adam Williamson 2023-10-03 17:42:16 UTC

Deferred to F40 per https://pagure.io/fesco/issue/3059#comment-876796 .

Comment 4 Adam Williamson 2023-10-19 19:26:21 UTC

Per discussion with David on Matrix https://matrix.to/#/#cloud:fedoraproject.org , this Change was actually completed for F39, so moving it back there and marking ON_QA.

Comment 5 Aoife Moloney 2023-11-14 18:57:27 UTC

F39 was released on November 7th, so I am closing this tracker. If this Change was not completed, please notify me ASAP.

Comment 6 Miroslav Vadkerti 2023-12-04 16:02:37 UTC

Well, it does not seem to work:

Looking at 125523088429/Fedora-Cloud-Base-39-20231204.0.x86_64-hvm-us-east-1-gp3-0 it has boot method unset, i.e. `-`.
I would expect `uefi-preferred`

https://us-east-1.console.aws.amazon.com/ec2/home?region=us-east-1#ImageDetails:imageId=ami-04cc75b7613fdcc2f

So I cannot confirm it happened, same for Rawhide.

Comment 7 Miroslav Vadkerti 2023-12-04 16:05:08 UTC

I have filled:

https://pagure.io/fedora-infrastructure/issue/11660

Let's continue there