Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 872413

Summary: LVMError: vgreduce failed for VolGroup00: running lvm vgreduce --config devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|","r|/VolGroup00$|","r|/sda2$|"] } --removemissing --force VolGroup00 failed
Product: Red Hat Enterprise Linux 7 Reporter: Xiaowei Li <xiaoli>
Component: lvm2Assignee: LVM and device-mapper development team <lvm-team>
lvm2 sub component: Default / Unclassified QA Contact: cluster-qe <cluster-qe>
Status: CLOSED NOTABUG Docs Contact:
Severity: urgent    
Priority: urgent CC: agk, heinzm, jbrassow, msnitzer, prajnoha, prockai, qcai, thornber, zkabelac
Version: 7.0Keywords: Triaged
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: 2012-12-07 06:55:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: release
none
File: product
none
File: type
none
File: ifcfg.log
none
File: storage.log
none
File: version
none
File: environ
none
File: executable
none
File: anaconda.log
none
File: syslog
none
File: hashmarkername
none
File: packaging.log
none
File: cmdline_file
none
File: ks.cfg
none
File: anaconda-tb
none
File: program.log none

Description Xiaowei Li 2012-11-02 02:53:15 UTC
Description of problem:
hit this issue when finishing the automatical partition

Version-Release number of selected component:
anaconda-18.22

Additional info:
libreport version: 2.0.17
cmdline:        /usr/bin/python  /sbin/anaconda
kernel:         3.6.0-0.28.el7.x86_64

description:
:The following was filed automatically by anaconda:
:anaconda 18.22 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicelibs/lvm.py", line 297, in vgreduce
:    raise LVMError("vgreduce failed for %s: %s" % (vg_name, msg))
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 2158, in _destroy
:    lvm.vgreduce(self.name, [], rm=True)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 816, in destroy
:    self._destroy()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 286, in execute
:    self.device.destroy()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 323, in processActions
:    action.execute()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 293, in doIt
:    self.devicetree.processActions()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 131, in turnOnFilesystems
:    storage.doIt()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 113, in doInstall
:    turnOnFilesystems(storage)
:  File "/usr/lib64/python2.7/threading.py", line 504, in run
:    self.__target(*self.__args, **self.__kwargs)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run
:    threading.Thread.run(self, *args, **kwargs)
:LVMError: vgreduce failed for VolGroup00: running lvm vgreduce --config  devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|","r|/VolGroup00$|","r|/sda2$|"] }  --removemissing --force VolGroup00 failed

Comment 1 Xiaowei Li 2012-11-02 02:53:18 UTC
Created attachment 636912 [details]
File: release

Comment 2 Xiaowei Li 2012-11-02 02:53:21 UTC
Created attachment 636913 [details]
File: product

Comment 3 Xiaowei Li 2012-11-02 02:53:24 UTC
Created attachment 636914 [details]
File: type

Comment 4 Xiaowei Li 2012-11-02 02:53:32 UTC
Created attachment 636915 [details]
File: ifcfg.log

Comment 5 Xiaowei Li 2012-11-02 02:53:36 UTC
Created attachment 636916 [details]
File: storage.log

Comment 6 Xiaowei Li 2012-11-02 02:53:39 UTC
Created attachment 636917 [details]
File: version

Comment 7 Xiaowei Li 2012-11-02 02:53:43 UTC
Created attachment 636918 [details]
File: environ

Comment 8 Xiaowei Li 2012-11-02 02:53:46 UTC
Created attachment 636919 [details]
File: executable

Comment 9 Xiaowei Li 2012-11-02 02:53:49 UTC
Created attachment 636920 [details]
File: anaconda.log

Comment 10 Xiaowei Li 2012-11-02 02:53:53 UTC
Created attachment 636921 [details]
File: syslog

Comment 11 Xiaowei Li 2012-11-02 02:53:55 UTC
Created attachment 636922 [details]
File: hashmarkername

Comment 12 Xiaowei Li 2012-11-02 02:53:58 UTC
Created attachment 636923 [details]
File: packaging.log

Comment 13 Xiaowei Li 2012-11-02 02:54:00 UTC
Created attachment 636924 [details]
File: cmdline_file

Comment 14 Xiaowei Li 2012-11-02 02:54:03 UTC
Created attachment 636925 [details]
File: ks.cfg

Comment 15 Xiaowei Li 2012-11-02 02:54:08 UTC
Created attachment 636926 [details]
File: anaconda-tb

Comment 16 Xiaowei Li 2012-11-02 02:54:11 UTC
Created attachment 636927 [details]
File: program.log

Comment 17 Xiaowei Li 2012-11-02 06:16:18 UTC
The root cause is that the VolGroup00 contains 3 PVs, but only 1 PV is discovered. The previous anaconda ( in RHEL6.3 ) support to re-initialize the LVM layout to work around this. 

This new anaconda should also support to handle this.

Comment 19 Zdenek Kabelac 2012-11-06 10:27:23 UTC
From the attachment in  Comment 16   it seems obvious the reason for failure is:

ERR program:   Volume group "VolGroup00" not found

Do you believe there exists this Volume group in the system when this operation is executed?

We would need to see further output of commands  like  pvs/vgs/lvs
but for now it rather looks like Anaconda bug and more diagnostic operations are needed for this case.

Are you able to modify anaconda scripts to insert more commands before vgreduce ?

Comment 20 Alasdair Kergon 2012-11-07 16:16:13 UTC
Perhaps someone who understands the anaconda logs could explain which devices form part of VolGroup00 and which were meant to be removed by the vgreduce command.  (I can't spot this information myself.)

And rerun the vgreduce command with -vvvv (or logging to file enabled in lvm.conf) so you can see what the vgreduce command actually saw, to compare against what you expected it to see.

Comment 21 Xiaowei Li 2012-11-08 11:08:14 UTC
I will do some investigation on this issue.

Comment 24 Xiaowei Li 2012-11-16 07:45:14 UTC
I will reproduce this when the h/w is available.

Comment 25 Xiaowei Li 2012-12-07 06:55:05 UTC
cannot reproduce it via the tree RHEL-7.0-20121129.0