Bug 232812 - f7-test2 does not put boot files in migrated /boot partition
f7-test2 does not put boot files in migrated /boot partition
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Cantrell
Depends On:
Blocks: FC7Blocker
  Show dependency treegraph
Reported: 2007-03-18 06:15 EDT by Allen Kistler
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-20 15:55:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Allen Kistler 2007-03-18 06:15:58 EDT
Description of problem:
During installation, the installer migrates existing /boot from ext2 to ext3. 
f7 / is a separate partition from existing / and is formatted new.  /boot is
migrated successfully to ext3.  /etc/fstab entries are set up successfully
(i.e., separate entry for /boot).  However, system.map, config, grub directory,
initrd, and vmlinuz are installed into /boot directory on / partition, not into
/boot partition.

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

How reproducible:
I only tried once, but I expect I could do it always.

Steps to Reproduce:
1. Start with existing ext2 older installation
2. In installer, migrate /boot partition from ext2 to ext3
3. In installer, format fresh / partition for f7-test2

Actual results:
f7 /boot files are in /boot directory on / partition

Expected results:
f7 /boot files should be in /boot partition

Additional info:
hda1 /boot (common to fc5 and f7)
hda2 /     (fc5)
hda3 swap  (common to fc5 and f7)
hda4 /     (f7)

Conjecture: The migration of the /boot partition from ext2 to ext3 appears to
result in the /boot partition not being mounted during installation.
Comment 1 David Cantrell 2007-04-20 15:55:10 EDT
Tested this in rawhide today and it appears to be working correctly now.

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