Bug 172378 - /root/anaconda-ks.cfg fails when used for installation
Summary: /root/anaconda-ks.cfg fails when used for installation
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2005-11-03 15:12 UTC by James Laska
Modified: 2013-09-02 06:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-11-03 21:14:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/root/anaconda-ks.cfg (1.05 KB, text/plain)
2005-11-03 15:12 UTC, James Laska
no flags Details

Description James Laska 2005-11-03 15:12:12 UTC
# TREE rawhide-20051103
# ARCH x86_64

Kickstart install using pykickstart generated anaconda-ks.cfg fails at
partitioning step.  It is not happy with --size=0 despite the --grow option. 
I'm not sure how it printed "--size=0" considering the pykickstart code paths
have a conditional check:

            if part.size != 0:
                str = str + " --size=%d" % part.size
            if part.size > 0:
                str = str + " --size=%d" % part.size

However, if we are going through anaconda/partitions.py Partitions::writeKS()
then it appears possible that --size=0

                if request.size == 0:

Steps to reproduce:
 1) perform a manual installation
 2) perform a kickstart installation using /root/anaconda-ks.cfg generated in step#1

"Error Parsing Kickstart Config"

The following error was found while parsing your kickstart 

The following problem occured on line 20 of the kickstart file:

Partition requires a size specification

                 [ Reboot ]


[ /root/anaconda-ks.cfg used for installation ]
 18 clearpart --all --drives=sda
 19 part /boot --fstype ext3 --size=100 --ondisk=sda
 20 part pv.3 --size=0 --grow --ondisk=sda
 21 volgroup VolGroup00 --pesize=32768 pv.3
 22 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
 23 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=432
--grow --maxsize=864

Comment 1 James Laska 2005-11-03 15:12:12 UTC
Created attachment 120690 [details]

Comment 2 James Laska 2005-11-03 16:06:05 UTC
update ... if I remove the entire --size=0 specification from line 20, anaconda
indicates that --size is required.  Using a --size=100 was able to work around
the problem.

Comment 3 Chris Lumens 2005-11-03 21:14:40 UTC
--size=0 --grow is legal and should be allowed.  Fixed.

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