Bug 1024507 - anaconda fails to warn that it is creating an unbootable system (or make it bootable)
Summary: anaconda fails to warn that it is creating an unbootable system (or make it b...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-29 20:00 UTC by Bill Nottingham
Modified: 2014-03-17 03:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-13 18:24:12 UTC
Target Upstream Version:

Attachments (Terms of Use)
created anaconda-ks.cfg (1.18 KB, text/plain)
2013-10-29 20:00 UTC, Bill Nottingham 		no flags Details
storage log (139.87 KB, text/plain)
2013-10-29 20:00 UTC, Bill Nottingham 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Bill Nottingham 2013-10-29 20:00:25 UTC 
Created attachment 817167 [details]
created anaconda-ks.cfg

Description of problem:

I have a two disk system. I chose to install to the second disk (selected second disk, chose autopart).

anaconda created, without warning, a system that would not boot unless I went into the bios and switched the boot order. (It just continued to boot the first disk.)

Version-Release number of selected component (if applicable):

20131029 nightly
Comment 1 Bill Nottingham 2013-10-29 20:00:56 UTC 
Created attachment 817168 [details]
storage log
Comment 3 David Cantrell 2013-12-13 18:24:12 UTC 
(From pjones):

I think it's NOTABUG. We have no way of knowing the FW boot order (AFAIK) except on EDD systems, so there's no way for us to claim we know whether the system will be bootable or not.
Note You need to log in before you can comment on or make changes to this bug.