Bug 962086 - cannot skip install of bootloader
cannot skip install of bootloader
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
19
i686 Linux
unspecified Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-11 12:22 EDT by John Reiser
Modified: 2013-07-05 14:12 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-05 14:12:42 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
/tmp/storage.log from installer (209.98 KB, text/plain)
2013-05-11 12:28 EDT, John Reiser
no flags Details

  None (edit)
Description John Reiser 2013-05-11 12:22:41 EDT
Description of problem: There isn't any way to skip installation of bootloader.

Version-Release number of selected component (if applicable):
Fedora-19-Beta-TC4-i386-netinst
anaconda-19.25-1

How reproducible: every time


Steps to Reproduce:
1. boot Fedora-19-Beta-TC4-i386-netinst.iso from CD
2. Select drives; click "Full disk summary and bootloader"
3. Highlight drive with existing bootloader (green check mark)
  
Actual results: Button remains "Set as boot device" instead of changing to "Do not install bootloader".  Presumably this means that the existing bootloader will be replaced; I cannot afford to verify that.


Expected results: When selecting the drive which has existing bootloader (in the "Full disk summary and bootloader" dialog) then the buttom "Set as boot device" should change to "Do not install bootloader", and the green check mark should be erased, and the installer should not install a bootloader, nor make any changes to the existing bootloader


Additional info: This worked correctly in TC2.
Comment 1 John Reiser 2013-05-11 12:28:12 EDT
Created attachment 746602 [details]
/tmp/storage.log from installer

Here is the storage.log.  It is from the same machine and the same initial state, although this session might have included some different choices regarding selection of swap space.  In both cases I pushed the hardware reset button before starting the install, so I believe that there were no actual changes to on-disk state.
Comment 2 John Reiser 2013-05-11 14:29:19 EDT
Works correctly in TC3, too. The button changes to "Do not install bootloader"; clicking it removes the green check mark in the Boot column, and changes the button to "Set as Boot Device".  So the regression was between TC3 and TC4.
Comment 3 David Shea 2013-07-05 14:12:42 EDT
Works correctly in F19 final

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