Bug 997629 - change EFI to use currentboot
Summary: change EFI to use currentboot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 0.14.2
Assignee: Raymond Mancy
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks: 994677
TreeView+ depends on / blocked
 
Reported: 2013-08-15 20:03 UTC by Bill Peck
Modified: 2018-02-06 00:41 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-11-07 01:47:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Bill Peck 2013-08-15 20:03:18 UTC
Description of problem:

Currently to support netboot(PXE) on efi or UEFI the label must be Netboot.  Some UEFI bios's don't support changing the label making this difficult.  Worse, some use the same label for multiple NIC's making it difficult to select via label.

This patch switches the code to rely on BootCurrent which will always be Netboot if the system was doing a Netboot install.

This means the admin just needs to make sure the initial bootorder has netboot first and subsequent installs will keep it first.

Version-Release number of selected component (if applicable):
0.14.1

diff --git a/Server/bkr/server/snippets/rhts_post b/Server/bkr/server/snippets/rhts_post
index cf857a4..297d888 100644
--- a/Server/bkr/server/snippets/rhts_post
+++ b/Server/bkr/server/snippets/rhts_post
@@ -79,8 +79,7 @@ fi
 # If efibootmgr exists then re-order boot options
 if [ -x '/usr/sbin/efibootmgr' ]; then
     BOOT=$(/usr/sbin/efibootmgr -v | grep BootOrder | awk '{print $2}' | awk -F, '{print $1}')
-    EFI=$(/usr/sbin/efibootmgr -v | grep Boot$BOOT | awk '{print $NF}')
-    PXE_SLOT=$(/usr/sbin/efibootmgr -v | grep -Ei '(netboot|pxe)' |head -n 1 |cut -c5-8)
+    PXE_SLOT=$(/usr/sbin/efibootmgr -v | grep -i BootCurrent | awk '{print $2}')
     # If There is no Netboot Entry we can't continue
     # You have to manually setup a Netboot entry first
     # from EFI maint menu.

Comment 1 Bill Peck 2013-08-15 20:06:14 UTC
http://gerrit.beaker-project.org/#/c/2164/

Comment 3 Dan Callaghan 2013-08-15 23:10:24 UTC
Ah that sounds very neat, thanks Bill!

Comment 4 Raymond Mancy 2013-08-27 03:48:22 UTC
http://gerrit.beaker-project.org/#/c/2164/

Comment 8 Russ Anderson 2013-09-17 19:25:26 UTC
Any ETA as to when this fix shows up on the Beaker systems?

Comment 9 Nick Coghlan 2013-09-18 00:11:37 UTC
The upstream 0.15.0 preliminary release will happen this week. The timing of the deployment to Red Hat's primary production instance depends on how acceptance testing of the release goes next week, but if all goes well, it should be available first week of October.

Comment 10 Nick Coghlan 2013-10-03 02:30:16 UTC
Beaker 0.15 has been released.

Comment 11 Raymond Mancy 2013-10-23 01:57:10 UTC
This change has been nominated to be back ported to the 0.14 branch, to be released as part of the next maintenance release 0.14.2.

Comment 12 Nick Coghlan 2013-10-25 06:36:34 UTC
Adjusting target milestone to make the changes backported to 0.14.2 easier to identify. 0.15.0 has enough significant regressions that it shouldn't be used, so the change means that 0.15.1 can be effectively reidentified as the union of that tag and the 0.14.2 target milestone.

Comment 15 Nick Coghlan 2013-11-07 01:47:38 UTC
Closing as addressed in Beaker 0.14.2.


Note You need to log in before you can comment on or make changes to this bug.