RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2005516 - NVMe FC Boot From SAN OS installation: Installation error "failed to set new efi boot target"
Summary: NVMe FC Boot From SAN OS installation: Installation error "failed to set new ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: efivar
Version: 9.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: 9.0
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-17 20:57 UTC by Michael
Modified: 2022-05-17 16:38 UTC (History)
11 users (show)

Fixed In Version: efivar-38-2.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 16:03:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:
ricky.armas: needinfo-

Attachments (Terms of Use)
Log files from during installation (11.72 MB, application/zip)
2021-09-17 20:57 UTC, Michael 		no flags Details
Output of strace (86.25 KB, text/plain)
2021-12-08 19:29 UTC, Michael 		no flags Details
Tree output of nvme0n1 device (7.72 KB, text/plain)
2021-12-08 19:31 UTC, Michael 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-97493 0 None None None 2021-09-17 20:59:36 UTC
Red Hat Issue Tracker RTT-4180 0 None None None 2022-02-02 14:43:02 UTC
Red Hat Issue Tracker RTT-4181 0 None None None 2022-02-02 14:43:09 UTC
Red Hat Product Errata RHBA-2022:4050 0 None None None 2022-05-17 16:03:17 UTC

Description Michael 2021-09-17 20:57:29 UTC 
Created attachment 1824059 [details]
Log files from during installation

Description of problem:
While installing RHEL-9.0.0-20210823.6 onto an NVME FC boot device via Boot From SAN, the OS installation reports the following error:
"Failed to set new efi boot target. This is most likely a kernel or firmware bug."

Version-Release number of selected component (if applicable):
RHEL-9.0.0-20210823.6

How reproducible:
This is only reproducible using a software package that is currently only available to internal Broadcom, however a similar issue was brought up in 2019 for RHEL 8.1.0, and I suspect that the root cause is the same.

Steps to Reproduce:
1.
2.
3.

Actual results:
I've attached the log files from /tmp of the install. In /tmp/program.log we see the following:

INFO:program:Running in chroot '/mnt/sysroot'... efibootmgr -c -w -L Red Hat Enterprise Linux -d /dev/nvme0n1 -p 1 -l \EFI\redhat\shimx64.efi
INFO:program:Could not prepare Boot variable: No such file or directory
DEBUG:program:Return code: 5


Expected results:


Additional info:
The previous BZ fixed the issue in version efivar-37-2.el8.
The version in this nightly build is 37-17.el9.
Comment 1 Michael 2021-11-03 23:27:15 UTC 
This issue is still seen in the most recent RHEL 9 Beta I tested (10/26/2021 build)
Comment 2 Laurie Barry 2021-11-04 14:04:42 UTC 
Sirius - Can you please help is get this moving.  It's been sitting since mid September without movement.

Thank you
Laurie
-----------------------------------------------

Do you know how we can get RH's attention with this? We need it to get fixed before RHEL 9 GAs. Preferably before.
To give some context,  the issue we are observing was actually seen in a previous version of efivars (RHEL 7.8, 7.9 and 8.1) and 
fixed (in RHEL8.2 or 8.3) but the bug looks like it's returned. When installing on BFS it throws an error message about not being 
able to install the boot loader.
Comment 4 Sirius Rayner-Karlsson 2021-11-08 15:11:06 UTC 
Hi there Laurie,

With help from others, we're asking for help from Javier that dealt with BZ#1755645 in RHEL8.

Kind regards,

/S
Comment 6 Robbie Harwood 2021-11-24 16:36:12 UTC 
It might help to have more information about what efivar is doing here.  One way would be strace output of the failing efibootmgr invocation.
Comment 7 Michael 2021-12-08 19:29:25 UTC 
Created attachment 1845322 [details]
Output of strace

Ran the following command and captured the output:

strace -o /tmp/log.txt -s 256 efibootmgr -c -w -L "Ricky RHEL9 v1" -d /dev/nvme0n1 -p 1 -l \\EFI\\redhat\\shimx64.efi
Comment 8 Michael 2021-12-08 19:31:00 UTC 
Created attachment 1845323 [details]
Tree output of nvme0n1 device

Capture of the output of the following command:

# tree /sys/block/nvme0n1/device > /tmp/tree.txt
Comment 9 Robbie Harwood 2021-12-08 23:14:35 UTC 
Thanks.  Are you able to try a test build?  If so, could you let me know what happens with rpms in https://people.redhat.com/~rharwood/multipath.tar and provide strace if it fails?
Comment 10 ricky.armas 2021-12-08 23:32:01 UTC 
I verified that the issue is resolved using that test build.
Comment 18 errata-xmlrpc 2022-05-17 16:03:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: efivar), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:4050
Note You need to log in before you can comment on or make changes to this bug.