Bug 245315

Summary: Fedora 7 kickstart installation failing with <= 256 MB RAM
Product: [Fedora] Fedora Reporter: Christian Mandery <rhbugzilla>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 7CC: linux
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-30 14:29:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Christian Mandery 2007-06-22 12:24:00 UTC
Description of problem:
When trying to install Fedora 7 with the kickstart mechanism, the installer
fails with a message saying that the partition selected as the root partition
(e.g. sda1) could not be found.

If I try a manual installation (no kickstart) on the same machine, anaconda
tells me before starting the real installation that the system lacks enough
memory for the installation and that it will create a swap partition instantly
(which happens before the normal partitioning step).

Perhaps this pre-installation swap creation process screws up the later
partitioning done by kickstart.

This is the relevant part of the kickstart config:
bootloader --location=mbr
clearpart --all --initlabel
part swap --recommended
part / --fstype ext3 --size 1 --grow

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

Steps to Reproduce:
1. Install with kickstart configuration for anaconda on a computer with 256 MB
RAM (or less).
  
Actual results:
Root partition device node does not exist. Installation aborts with an error
message.

Expected results:
Installer should work with 256 MB RAM without additional swap or respect the
kickstart configuration when creating the swap partition.

Comment 1 Chris Lumens 2007-11-30 05:25:18 UTC
I believe Jeremy's recent changes to when the partitioning steps get run in the
dispatcher should fix this up as all swap will be activated early on now.

Comment 2 Jeremy Katz 2007-11-30 14:29:16 UTC
Yes, this should be helped with the early partitioning commit that we're doing now