Bug 1049552

Summary:	efibootmgr called too soon, if it fails then post install scripts don't run and resulting system is really messy to clean up
Product:	[Fedora] Fedora	Reporter:	Chris Murphy <bugzilla>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	anaconda-maint-list, fche, g.kaviyarasu, jonathan, kparal, rgm, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-16 14:41:55 UTC	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:

Description Chris Murphy 2014-01-07 18:09:26 UTC

Description of problem:
There are some UEFI and maybe kernel bugs that cause the efibootmgr command to write NVRAM entries to fail. When that fails, anaconda fails to complete installation tasks. Because grub and shim packages have a fallback contingency for no NVRAM entry, we should move the anaconda issued efibootmgr command later than present, pretty much the last possible step. That way the root and user configurations are written, /etc/default/grub can be written, grub.cfg produced, and so on. So even if the NVRAM write fails, chances are the system can still boot.

Present behavior, it will not boot without a lot of manual intervention because so many post install things failed to complete.

Version-Release number of selected component (if applicable):
anaconda-20-25-1

How reproducible:
Always, *if* there is failure to write NVRAM entry via efibootmgr.

Steps to Reproduce:
1.
2.
3.

Actual results:
If NVRAM write fails, anaconda stops, no post install completes, system not bootable.

Expected results:
Do all the other stuff first, including post install, and cause efibootmgr to run after all of that. Then if it fails, we can probably still boot (and if not, there's still no harm done).

Additional info:


Bug 1006304
Bug 1006304

Comment 1 Robert Moskowitz 2014-01-07 19:21:27 UTC

Add Bug 1047993
	
where I report the efibootmgr fails due to kernel problems.

Comment 2 Chris Murphy 2014-04-16 02:43:12 UTC

This bug can probably be closed, see bug 1006304 comment 41 (and 11).

Comment 3 David Shea 2015-01-16 14:41:55 UTC

Closing per comment 2