Bug 1292911 - clearpart zerombr not removing lvm data RHEL-6.7 Server i386
clearpart zerombr not removing lvm data RHEL-6.7 Server i386
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Anaconda Maintenance Team
Release Test Team
Depends On:
  Show dependency treegraph
Reported: 2015-12-18 12:27 EST by andrew
Modified: 2015-12-21 17:25 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-21 17:25:54 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description andrew 2015-12-18 12:27:36 EST
Description of problem:

clearpart zerombr not removing lvm data RHEL-6.7 Server i386 

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

How reproducible: 100%

Steps to Reproduce:
1. Install RHEL-6.7 Server i386 to 4 disks
2. reboot 
3. Install RHEL-6.7 Server i386 to 3 disks with a kickstart with clearpart zerombr

Actual results:

 System try's to boot and there are two homes and two roots and two swaps.

Expected results:

clearpart zerombr should of cleared all lvm data on the disks.

Additional info:
My work around is to dd /dev/zero 100MB to the disks before the install. or in the %post to the disk I'm not installing to.
Comment 2 Chris Lumens 2015-12-18 15:28:56 EST
Please attach your kickstart file and /tmp/anaconda.log to this bug report.  Thanks.
Comment 6 Brian Lane 2015-12-21 17:11:53 EST
You told it to only use sda, it won't touch the other disk. You need to make sure you clean up the metadata before reinstalling.
Comment 7 RHEL Product and Program Management 2015-12-21 17:25:54 EST
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

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