Bug 885381 - F18 anaconda leaves more than one disk shown as a 'boot device' when multiple disks are selected and one changes the boot device
Summary: F18 anaconda leaves more than one disk shown as a 'boot device' when multiple...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 895068 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-08 23:53 UTC by Reartes Guillermo
Modified: 2013-03-12 14:27 UTC (History)
7 users (show)

Fixed In Version: anaconda-19.2-1
Clone Of:
Environment:
Last Closed: 2013-01-16 20:54:29 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
screenshot of the issue (79.01 KB, image/png)
2012-12-08 23:53 UTC, Reartes Guillermo 		no flags Details
View All

Description Reartes Guillermo 2012-12-08 23:53:31 UTC 
Created attachment 660156 [details]
screenshot of the issue

Description of problem:

It is possible for anaconda to shown more than one 'boot device' at the same time under some circumstances.

Version-Release number of selected component (if applicable):
F18 TC1 (anaconda 18.36)

How reproducible:
always

Steps to Reproduce:

0. Enter Storage: Installation Destination and select more than one disk.
1. Press 'Full disk summary...' to display the SELECTED DISKS dialog.
2. Select the first disk and click 'Do not install boot-loader'
3. Select the second disk and click 'Set as Boot Device'
4. In the attached screen-shot, more than one disk appears as a BOOT DEVICE.
  
Actual results:
more than one disk appears as a 'boot device'
Comment 1 Chris Lumens 2012-12-10 17:01:01 UTC 
I'll send off a patch for master for this.  If you think it needs to be in F18, it'll need to be made a blocker or NTH.
Comment 2 Chris Lumens 2013-01-16 20:56:55 UTC 
*** Bug 895068 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.