Bug 895693 - Fails to install bootloader when using kickstart with no storage configuration
Summary: Fails to install bootloader when using kickstart with no storage configuration
Keywords:
Status: CLOSED DUPLICATE of bug 887254
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-15 19:24 UTC by Yanko Kaneti
Modified: 2013-01-18 15:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-18 15:47:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


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