Bug 39966

Summary: mismatch between documentation and kickstart partition options
Product: [Retired] Red Hat Linux Reporter: Alex Vorobiev <sasha>
Component: anacondaAssignee: Brent Fox <bfox>
Status: CLOSED CURRENTRELEASE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-05-10 14:15:21 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 Alex Vorobiev 2001-05-09 23:06:22 UTC
Description of problem:
as per
http://www.redhat.com/support/manuals/RHL-7-Manual/ref-guide/s1-kickstart2-commands.html,
--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
message.

How reproducible:
Always

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?

thanks

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
http://www.redhat.com/support/manuals/RHL-7.1-Manual/customization-guide/s1-kickstart2-options.html

Quoting from that:
--asprimary

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


Thanks for your report.  Resolving as 'Current Release'