Bug 135714

Summary: part command requires size, not provided in anaconda-ks.cfg
Product: [Fedora] Fedora Reporter: david d zuhn <zoo>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED CURRENTRELEASE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: nobody+pnasrat
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-06-21 15:39:06 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:
Attachments:
Description Flags
The KS file as created during my manual installation none

Description david d zuhn 2004-10-14 16:47:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040808 Firefox/0.9.3

Description of problem:
The /root/anaconda-ks.cfg as written by the installer during a manual
installation of FC3T3 isn't syntactically correct for use during a
real install.

In particular, the part commands as written do not have a --size
option, just --grow.  Yet, when installing with this file, anaconda
will die because of this missing option.

I can make arguments for two possible ways to resolve this.  

First, write an appropriate --size argument that matches the current
hardware when creating the file during an install.  

Second, when --grow is provided on a command line, --size should be
optional.  In this case, the partition should use all available space.
 When --size is provided with --grow, the argument provides the
minimum size the partition should be.



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


How reproducible:
Always

Steps to Reproduce:
1. install FC3t3
2. use created /root/anaconda-ks.cfg for an installation
3. 
    

Actual Results:  Installation dies, due to missing argument.  It's
kind of an ugly death, involving python tracebacks instead of human
readable error messages.

Expected Results:  The same installation I just performed should be
performed again.

Additional info:

Comment 1 david d zuhn 2004-10-14 16:49:18 UTC
Created attachment 105204 [details]
The KS file as created during my manual installation

I used this file as the basis for my automatic installation ks file.  I
uncommented the clearpart, part, volgroup, and logvol commands.

Comment 2 Jeremy Katz 2004-10-17 21:58:06 UTC
Fixed in CVS