Bug 39966 - mismatch between documentation and kickstart partition options
Summary: mismatch between documentation and kickstart partition options
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-05-09 23:06 UTC by Alex Vorobiev
Modified: 2007-04-18 16:33 UTC (History)
0 users

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

Attachments (Terms of Use)

Description Alex Vorobiev 2001-05-09 23:06:22 UTC
Description of problem:
as per
--asprimary option for part command must be used with a numeric argument:
--asprimary <N>

            Forces auto allocation as a primary partition <N> or fail. <N>
can be 1 through 4. 

the anaconda kickstart.py code doesn't support that.  as per the code,
asprimary should not have any arguments.  the install fails with an error

How reproducible:

Steps to Reproduce:
1.  add lines to kickstart config file like
part /  --size 1024 --asprimary
2.   start kickstart install
3.   watch it fail

Actual Results:  install fails with an error:

partition command requires one anonymous argument

Expected Results:  partition created as a primary partition

Additional info:

this may also affect 7.1, didn't check.

also confused about --onprimary and --asprimary options.  i tried them in
every possible combination and permutation, and every time the
autopartitioning failed with the following error:
	Failed to allocate '/': no free primary
and so on, and switches to disk druid.  i am familiar with the trick to
specify a /boot partition to make sure that kickstart makes it a primary
partition.  but the other options that are supposed to specify whether the
partition is primary or not, don't work.
am i not using them correctly?


Comment 1 Alex Vorobiev 2001-05-10 14:15:16 UTC
in the Steps to reproduce section, instead of 

	part /  --size 1024 --asprimary

please read:

	part /  --size 1024 --asprimary 1

Comment 2 Brent Fox 2001-05-10 20:30:10 UTC
I think this has been fixed in the 7.1 documentation.  The 7.1 Reference Guide
kickstart guide is available at

Quoting from that:

    Forces automatic allocation of the partition as a primary partition or the
partitioning will fail.

Thanks for your report.  Resolving as 'Current Release'

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