Bug 2383329

Summary: pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug.
Product: [Fedora] Fedora Reporter: Peng Fan <peng.fan>
Component: anacondaAssignee: anaconda-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: anaconda-maint, kkoukiou, pbrobinson, peng.fan, w
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
Whiteboard: abrt_hash:558a9fefa9ac9dd661664385d692bf707007601ca765de9f1a30c3298f62af97;VARIANT_ID=;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-12-11 08:47:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 245418    
Attachments:
Description Flags
File: anaconda-tb
none
File: backtrace
none
File: os_info
none
File: environ
none
File: syslog
none
File: description
none
File: storage.log
none
File: packaging.log
none
File: program.log
none
File: nmcli_dev_list
none
File: anaconda.log
none
File: lorax-packages.log
none
File: lsblk_output
none
File: dbus.log
none
File: packaging.log none

Description Peng Fan 2025-07-25 01:13:24 UTC
Description of problem:
Install Fedora-Everything-netinst-aarch64-Rawhide-20250724.n.0.iso on NXP i.MX8MP-EVK(AARCH64).

In step "Installing boot loader", it reports the error.

Version-Release number of selected component:
anaconda-43.31


The following was filed automatically by anaconda:
anaconda 43.31 exception report
Traceback (most recent call first):
  File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 509, in _handle_method_error
    raise exception from None
  File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 483, in _get_method_reply
    return self._handle_method_error(error)
  File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 450, in _call_method
    return self._get_method_reply(
  File "/usr/lib64/python3.14/site-packages/pyanaconda/ui/gui/spokes/installation_progress.py", line 76, in _on_installation_done
    self._task_proxy.Finish()
  File "/usr/lib/python3.14/site-packages/dasbus/signal.py", line 53, in emit
    callback(*args, **kwargs)
  File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 365, in _signal_callback
    callback(*unwrap_variant(parameters))
  File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 133, in _signal_callback
    callback(parameters, *callback_args)
pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug.

Additional info:
cmdline:        /usr/bin/python3  /usr/bin/anaconda
executable:     /usr/bin/anaconda
hashmarkername: anaconda
product:        Fedora
reason:         pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug.
package:        anaconda-43.31
release_type:   pre-release
type:           anaconda
release:        Fedora release 43 (Rawhide)
cmdline_file:   BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-E-dvd-aarch64-rawh rd.live.check
addons:         com_redhat_kdump
kernel:         6.16.0-0.rc7.60.fc43.aarch64
version:        rawhide

Comment 1 Peng Fan 2025-07-25 01:13:28 UTC
Created attachment 2098167 [details]
File: anaconda-tb

Comment 2 Peng Fan 2025-07-25 01:13:29 UTC
Created attachment 2098168 [details]
File: backtrace

Comment 3 Peng Fan 2025-07-25 01:13:30 UTC
Created attachment 2098169 [details]
File: os_info

Comment 4 Peng Fan 2025-07-25 01:13:31 UTC
Created attachment 2098170 [details]
File: environ

Comment 5 Peng Fan 2025-07-25 01:13:33 UTC
Created attachment 2098171 [details]
File: syslog

Comment 6 Peng Fan 2025-07-25 01:13:35 UTC
Created attachment 2098172 [details]
File: description

Comment 7 Peng Fan 2025-07-25 01:13:36 UTC
Created attachment 2098173 [details]
File: storage.log

Comment 8 Peng Fan 2025-07-25 01:13:38 UTC
Created attachment 2098174 [details]
File: packaging.log

Comment 9 Peng Fan 2025-07-25 01:13:40 UTC
Created attachment 2098175 [details]
File: program.log

Comment 10 Peng Fan 2025-07-25 01:13:41 UTC
Created attachment 2098176 [details]
File: nmcli_dev_list

Comment 11 Peng Fan 2025-07-25 01:13:42 UTC
Created attachment 2098177 [details]
File: anaconda.log

Comment 12 Peng Fan 2025-07-25 01:13:44 UTC
Created attachment 2098178 [details]
File: lorax-packages.log

Comment 13 Peng Fan 2025-07-25 01:13:45 UTC
Created attachment 2098179 [details]
File: lsblk_output

Comment 14 Peng Fan 2025-07-25 01:13:46 UTC
Created attachment 2098180 [details]
File: dbus.log

Comment 15 Peng Fan 2025-07-25 01:13:48 UTC
Created attachment 2098181 [details]
File: packaging.log

Comment 16 Peter Robinson 2025-07-25 14:48:18 UTC
This is because the device doesn't implement UEFI set variable. It should offer an option to continue.

It's been dealt with upstream with the following PR

https://github.com/rhboot/efivar/pull/282

But I'm not sure efivar has had a new release or that patch hasn't been pulled in yet.

Comment 17 Katerina Koukiou 2025-12-11 08:47:38 UTC

*** This bug has been marked as a duplicate of bug 2367837 ***