Bug 743378 - interactive kickstart ignores disk partition and volume creation commands
Summary: interactive kickstart ignores disk partition and volume creation commands
Keywords:
Status: CLOSED DUPLICATE of bug 641861
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-04 17:57 UTC by Mark J Strawcutter
Modified: 2011-10-04 18:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-04 18:18:39 UTC
Target Upstream Version:


Attachments (Terms of Use)

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 ***


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