Red Hat Bugzilla – Bug 149220
RHEL4 U2: Python exception while creating LVM2 volumes
Last modified: 2007-11-30 17:07:16 EST
Description of problem:
OS: RHEL4 Gold
Platform: PowerEdge 6650
Disks: 2 x (any capacity) disks connected to onboard Adaptec AIC-
7892P U160/m controller
-Disk 1 has a previous installation of RHEL4 with /boot(ext3) and
one LVM2 parition (volume group VolGroup00)
-Disk 2 has a previous installation of RHEL4 with /boot(ext3) and
one LVM2 partition (volume group VolGroup00) but from a different
During install, when automatic partitioning is selected and all
dialogs completed, anaconda throws a python exception (anaconda dump
file attached) while creating filesystems.
NOTE: This defect is seen ONLY when disks from a previous
installation of RHEL4 with LVM2 from two DIFFERENT machines are used.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RHEL4 with autopartioning on 2 machines (machine A and
machine B) with one disk each. Ensure that there are NO previous LVM
partitions on both the disks prior to installation
2. Connect disk from machine A to machine B so that machine B now
has two disks connected to it
3. Initiate RHEL4 installation on machine B. Choose
autopatitioning, complete all dialogs
1. Python exception is seen just before filesystems are created
2. Consecutive installs fail with the same exception.
Installation should have deleted the old partitions, created the new
LVM2 volumes and completed successfully.
dd if=/dev/zero of=/dev/sdb count=1 bs=512
and proceeding with the install does not throw the python exception
and install completes successfully.
Created attachment 111254 [details]
I believe this to be a duplicate of 144827, which is on our Update 1
*** This bug has been marked as a duplicate of 144827 ***
This bug is still present in RHEL4 Update1 beta 1.
I am not convinced that this is a duplicate of BZ144827. 144827 is PROD_READY
while this one is still reproducible on U1 Beta. I am adding this to Devzilla
so we can track this.
Reopening this issue as it is still reproducible as per Charles Rose
Paste from BZ144827 as this is pertinent to this bug:
Comment #19 From Charles Rose (email@example.com) on 2005-04-20 05:15 EST
On RHEL4 U1 Beta we see a Python exception:
I installed two identical PE2850 machines (A and B) with single SCSI disks (No
RAID) with the autopartitioning scheme. Disks on both machines were at SCSI
The partitions on both the disks (from machine A and machine B) were:
sda1 (ext3, /boot)
After installation, I moved the disk from machine B and plugged it in machine A
at SCSI ID1 and started the installation (GUI).
I chose to do a fresh Install with autopartition. After the package selection
screen where we usually see the "Formatting" messages, anaconda throws an
exception (file attached) during "lvmremove". Repeated attempts have the same
Created attachment 113502 [details]
Anaconda Dump 2
Here's the culprit text in the dumps:
, fsentry -- device: VolGroup00/LogVol01 mountpoint: swap
fsystem: swap format: 1
Unable to deactivate logical volume "LogVol01"
LogVol01 is currently being used as swap space, so lvremove will fail.
I can reproduce this independent of the drives Matt sent in; it's a problem
where you've got two VGs with the same name, and the LVM tools aren't consistent
in their determination of what constitutes "inconsistent metadata", so they'll
let you activate things but not remove or deactivate them.
I realize this is an older bug, but I'm marking it as a dupe of 168723, which is
already assigned to the LVM tools. And removing it from the proposed list.
(I'm also adding the associated Issue Trackers to that bug)
*** This bug has been marked as a duplicate of 168723 ***