Bug 743378

Summary: interactive kickstart ignores disk partition and volume creation commands
Product: Red Hat Enterprise Linux 6 Reporter: Mark J Strawcutter <mjstraw>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-04 18:18:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mark J Strawcutter 2011-10-04 17:57:02 UTC 
Description of problem:

Interactive kickstart install with ks.cfg containing the following:

clearpart --drives=sda --all
ignoredisk --drive=sdb
part /boot --ondisk=sda --fstype=ext4 --size=500
part pv.008002 --ondisk=sda --grow --size=1
volgroup vg_xyzzy --pesize=4096 pv.008002
logvol / --fstype=ext4 --name=lv_root --vgname=vg_xyzzy --grow --size=1024
logvol swap --name=lv_swap --vgname=vg_xyzzy --recommended

ignores those commands and creates default logical volumes lv_root, lv_home and lv_swap and uses host name in vgname instead of specified xyzzy

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


How reproducible:

perform interactive kickstart install with ks.cfg containing above commands

Steps to Reproduce:
1. perform interactive kickstart install with ks.cfg containing above commands
2. select option to review disk part/vol setup during install
3.
  
Actual results:

creates logical volumes for swap, / and /home

creates volume group with name based on host name

Expected results:

create logical volumes for swap and /

create volumen group with name specified

Additional info:
Comment 2 David Cantrell 2011-10-04 18:18:39 UTC 

*** This bug has been marked as a duplicate of bug 641861 ***