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

Summary: anaconda error: Failed to set new efi boot target. This is most likely a kernel or firmware bug.
Product: [Fedora] Fedora Reporter: Dominik 'Rathann' Mierzejewski <dominik>
Component: anacondaAssignee: Javier Martinez Canillas <fmartine>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: anaconda-maint-list, dan, fmartine, jonathan, kellin, pbrobinson, vanmeeuwen+fedora, vponcova, w
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
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
Anaconda storage log none

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.