Bug 984482

Summary: fedup incorrectly detecting EFI boot
Product: [Fedora] Fedora Reporter: Joergen Thomsen <jth>
Component: grubbyAssignee: Peter Jones <pjones>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: bcl, pjones, tflink, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:07:56 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:
Embargoed:

Description Joergen Thomsen 2013-07-15 11:12:13 UTC
Description of problem:
On a non-EFI system with the file structure of efi present, fedup is assuming that the BIOS is an EFI BIOS

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


How reproducible:
always

Steps to Reproduce:
1. fedup --network 19 --debuglog fedupdebug.log
2. at reboot no change in the boot menu
3.

Actual results:

grub.cfg is generated in the efi structure and not in /boot/grub2 with the call to linuxefi for all present kernel versions

Expected results:
grub.cfg is generated in /boot/grub2 with the call to linux


Additional info:

Comment 1 Will Woods 2013-07-16 16:26:50 UTC
All fedup does is call `new-kernel-pkg`.

Something about your system is confusing grubby/new-kernel-pkg so it's writing to the wrong place.

Reassigning to grubby.

Comment 2 Brian Lane 2013-07-17 16:49:25 UTC
Please include the relevant configuration files, preferably from before and after the fedup run. Also, what do you mean by 'the file structure of efi'? And how did it get that way?

Comment 3 Joergen Thomsen 2013-07-18 23:06:09 UTC
(In reply to Brian C. Lane from comment #2)
> Please include the relevant configuration files, preferably from before and
> after the fedup run. 

What do you mean by configuration files ?

> Also, what do you mean by 'the file structure of efi'?

 /boot/efi/EFI/fedora/grub.cfg

> And how did it get that way?

The motherboard had to be replaced with a non-EFI one

Comment 4 Brian Lane 2013-07-19 16:59:50 UTC
Ah! That explains it then, thanks.

Comment 5 Fedora End Of Life 2013-12-21 14:20:02 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2014-02-05 22:07:56 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.