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.
http://gerrit.beaker-project.org/#/c/2164/
Ah that sounds very neat, thanks Bill!
Any ETA as to when this fix shows up on the Beaker systems?
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.
Beaker 0.15 has been released.
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.
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.
Closing as addressed in Beaker 0.14.2.