-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
Enable insertion of the UEFI entry for container installations
-
8
-
False
-
None
-
False
-
Testable
-
Done
-
0% To Do, 0% In Progress, 100% Done
-
-
User Stories:
As a user, I want to be able to install image based system next to the existing installation, so that I can use multiboot and don't have to do manual adjustments.
Description:
Current implementation of the bootupd does not insert any UEFI entry to the installed system. This is not an issue in most of the cases because if there is no valid UEFI entry the UEFI will take the first disk for booting. However, in case of multiboot support this is starting to be an issue because the new system is not bootable.
This functionality is handled by bootupd but we need to enable it. Also it's quite new implementation, so it needs coverage by tests.
Acceptance criteria:
- When installing image based system with bootupd support the UEFI entry should be inserted.
- If leavebootorder is enabled the new UEFI entry will not get inserted.
- Kickstart test for coverage.
Third party ACKs:
All the third parties who should be informed of this issue please provide here an ACK in case you agree with this proposed issue. This issue will then be included for the next quarterly planning.
Name (Team) | ACK or comment below |
---|---|
jstodola@redhat.com (RTT) | |
rhn-support-sbarcomb (PX) | ack July 22nd 2024 |
sdubewar (Doc) |
- is cloned by
-
INSTALLER-4018 RHEL: Enable insertion of the UEFI entry for container installations
- New