Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1958902 - anaconda error: Failed to set new efi boot target. This is most likely a kernel or firmware bug.
Summary: anaconda error: Failed to set new efi boot target. This is most likely a kern...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 34
Hardware: aarch64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Javier Martinez Canillas
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2021-05-10 12:01 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2022-06-07 21:11 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-07 21:11:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Anaconda storage log (deleted)
2021-05-10 12:01 UTC, Dominik 'Rathann' Mierzejewski
no flags Details

Description Dominik 'Rathann' Mierzejewski 2021-05-10 12:01:11 UTC
Created attachment 1781672 [details]
Anaconda storage log

Description of problem:
When installing Fedora 34 on a Pinebook Pro, anaconda displays 

Version-Release number of selected component (if applicable):
34.24.9-1.fc34

How reproducible:
Always.

Steps to Reproduce:
1. On a Pinebook Pro, flash U-Boot to SPI following https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/
2. Write an F34 DVD ISO image with dd.
3. Run anaconda --vnc (built-in display doesn't work in Live image)
4. Install e.g. MATE on the built-in eMMC.

Actual results:
At the end of the installation, the following message is displayed:
Failed to set new efi boot target. This is most likely a kernel or firmware bug.
and I'm given an option to ignore or abort the installation. Ignoring works because U-Boot has no issues booting grub2 from EFI system partition.

Expected results:
No error message.

Additional info:
Anaconda storage log attached.

Comment 1 Peter Robinson 2021-05-11 18:14:38 UTC
So this isn't a anaconda bug, SetVariable is optional, and it needs to be dealt with lower in the stack. It's a soft failure and things work just fine anyway so it's not fatal.

Comment 2 Ben Cotton 2022-05-12 15:13:29 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-06-07 21:11:01 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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