| Summary: | anaconda fails to warn that it is creating an unbootable system (or make it bootable) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Bill Nottingham <notting> | ||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Release Test Team <release-test-team> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 7.0 | CC: | rvokal | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-12-13 18:24:12 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: | |||||||
| Attachments: |
|
||||||||
Created attachment 817168 [details]
storage log
(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. |
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