Bug 895693

Summary:	Fails to install bootloader when using kickstart with no storage configuration
Product:	[Fedora] Fedora	Reporter:	Yanko Kaneti <yaneti>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, sbueno, 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:	2013-01-18 15:47:56 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 Yanko Kaneti 2013-01-15 19:24:19 UTC

Description of problem:
For a long time I've been using a kickstart without any storage and password configuration for a minimal install that only interactively asks about the disk/partitioning and the root password.

With the F18 just proceeding with the manual storage configuration of an empty disk (just as you would do without kickstart) and not touching anything else produces an install without a bootloader. The anaconda storage log says.

INFO storage: skipping bootloader install per user request

I didn't really request anything bootloader specific, expectnig it to be installed by default.


Virtually the same storage configuration steps without a kickstart again on a empty disk actually installs the bootloader.

Comment 1 Chris Lumens 2013-01-18 15:47:56 UTC

This is basically the same as bug 887254, which I'll mark this as a dup of.

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