Description of problem: * Initiate a kickstart install with clearpart and partition data specified. Version-Release number of selected component (if applicable): * anaconda-11.5.0.47 How reproducible: Steps to Reproduce: 1. Initiate kickstart install with the following partition data # System bootloader configuration bootloader --location=mbr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part /boot --asprimary --fstype="ext3" --size=200 --label=BOOT part swap --fstype="swap" --recommended --label=SWAP part raid.01 --grow --size=2048 part raid.02 --grow --size=2048 part pv.02 --size=2048 raid pv.01 --device=0 --fstype="ext3" --level=RAID0 raid.01 raid.02 volgroup LVMONRAID --pesize=32768 pv.01 pv.02 logvol / --fstype="ext3" --grow --size=2048 --name=root --vgname=LVMONRAID Actual results: * installation pauses and prompts for a response to: "Error processing LVM. There is inconsistent LVM data on logical volume vg_test101-lv_root. You can reinitialize all related PVs(/dev/vda2) which will erase the LVM metadata, or ignore which will preserve the contents. [ Ignore ] [ Re-initialize ]" Expected results: * fully non-interactive kickstart install Additional info:
Does using the zerombr command work? According to the wiki, this command does the following: If zerombr is specified, any invalid partition tables found on disks are initialized. This will destroy all of the contents of disks with invalid partition tables. That seems to translate pretty well into LVM land too.
Odd, in trying to retest this, I now hit bug#497352. A bit confused now
Putting back into NEEDINFO for now. I hate how adding comments automatically takes it out of that state.
This should be fixed in the next build of anaconda by moving clearpart into the early kickstart pass.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping