Bug 886270

Summary: Anaconda Grub2-mkconfig does not detect Fedora 17 on a second drive
Product: [Fedora] Fedora Reporter: Leslie Satenstein <lsatenstein>
Component: os-proberAssignee: Hedayat Vatankhah <hedayatv>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 18CC: bcl, dcantrell, dennis, hedayatv, mads, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-12 18:35:57 EST Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Leslie Satenstein 2012-12-11 17:43:17 EST
Description of problem:

Two disk system. /dev/sda is empty (my test drive) and /dev/sdb is my regular drive
The regular drive has Ubuntu, and Fedora 17.

During the anacona installation, grub.cfg is created with 
Fedora 18 first,
Ubuntu    second
and no Fedora 17

However...

manually running grub2-mkconfig from root picks up all three operating systems.

This may be a situation where anaconda has the wrong grub2-mkconfig or wrong os-prober software.

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


How reproducible:

Do a DVD installation according to my disk layout.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Mads Kiilerich 2012-12-11 20:12:04 EST
Probably a duplicate of a bug I can't find. I'm sure Hedayat know where it is.
Comment 2 Hedayat Vatankhah 2012-12-12 09:02:10 EST
Is Fedora 17 installed on LVM or not?
Comment 3 Leslie Satenstein 2012-12-12 18:29:40 EST
Fedora 17 is installed with lvm ext4, as a vanilla DVD installation.

One quirk, it was a Fedora 16 upgrade to Fedora 17, using the pre and post upgrades.

But Ubuntu detected F17 and so did F18 using grub2-mkconfig 

I have no idea if the os-prober used by anaconda from the installation DVD is as current as the os-prober version that installed.  

I can always wipe the drive and redo the test.
Comment 4 Hedayat Vatankhah 2012-12-12 18:35:57 EST
Thank you for the description; the problem is not with the upgrade or os-prober version, it is about your Fedora 17 LVM partitions being inactive when the config is generated.

*** This bug has been marked as a duplicate of bug 825236 ***