Bug 1465317 - [RFE] Support searching and filtering EFI boot machines when submitting bkr jobs via bkr workflow cmdline
Summary: [RFE] Support searching and filtering EFI boot machines when submitting bkr ...
Keywords:
Status: CLOSED DUPLICATE of bug 1112439
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: 24
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-27 08:03 UTC by Emma Wu
Modified: 2017-08-15 07:25 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-08-15 07:25:51 UTC
Embargoed:

Attachments (Terms of Use)

Comment 1 Qiao Zhao 2017-07-03 01:53:09 UTC 
Because more and more partner request UEFI issue, and qe still can't run automation case on uefi machine. And we didn't know which one is uefi boot machine unless we install system and login.
So, please take a look. Thanks in advance!
Comment 2 Dan Callaghan 2017-08-15 07:25:51 UTC 
Although it is a bit of a hack, you can currently identify machines with EFI firmware (booting in EFI mode) by looking for key NETBOOT_METHOD with value "efigrub" or "grub2":

https://beaker.engineering.redhat.com/?systemsearch-0.table=Key%2FValue&systemsearch-0.keyvalue=NETBOOT_METHOD&systemsearch-0.operation=is&systemsearch-0.value=efigrub

https://beaker.engineering.redhat.com/?systemsearch-0.table=Key%2FValue&systemsearch-0.keyvalue=NETBOOT_METHOD&systemsearch-0.operation=is&systemsearch-0.value=grub2

Corresponding job XML filters are:

<key_value key="NETBOOT_METHOD" value="efigrub"/>

<key_value key="NETBOOT_METHOD" value="grub2"/>

For a less hackish proper solution to get detailed firmware info, there is bug 1112439.

*** This bug has been marked as a duplicate of bug 1112439 ***
Note You need to log in before you can comment on or make changes to this bug.