Bug 1332321

Summary: gi.overrides.BlockDev.LVMError: Process reported exit code 1280: Multiple VGs found with the same name: skipping fedora
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d16613f40cee11a7dbe2d2d0a6f009fe0a3a3abd1fa941112e5dd2951892d063;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 14:23:41 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: anaconda-tb
none
File: anaconda.log
none
File: dnf.log
none
File: environ
none
File: lsblk_output
none
File: lvm.log
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: syslog
none
File: ifcfg.log
none
File: packaging.log
none
lvdisplay output none

Description Adam Williamson 2016-05-02 22:57:15 UTC
Description of problem:
Installed F24 Beta 1.4 Server netinst x86_64 to a freshly created firmware RAID set, then booted back to the installer to try installing over the top of that install. Hit this crash on the welcome screen.

Version-Release number of selected component:
anaconda-24.13.4-1

The following was filed automatically by anaconda:
anaconda 24.13.4-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python3.5/site-packages/gi/overrides/BlockDev.py", line 420, in wrapped
    raise transform[1](msg)
  File "/usr/lib/python3.5/site-packages/blivet/devices/lvm.py", line 768, in _setup
    blockdev.lvm.lvactivate(self.vg.name, self._name)
  File "/usr/lib/python3.5/site-packages/blivet/devices/storage.py", line 386, in setup
    self._setup(orig=orig)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 1015, in addLV
    lv_device.setup()
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 1062, in handleVgLvs
    new_lv = addLV(lv)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 1142, in handleUdevLVMPVFormat
    self.handleVgLvs(vg_device)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 1489, in handleUdevDeviceFormat
    self.handleUdevLVMPVFormat(info, device)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 773, in addUdevDevice
    self.handleUdevDeviceFormat(info, device)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 260, in _addSlaveDevices
    self.addUdevDevice(slave_info)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 289, in addUdevLVDevice
    self._addSlaveDevices(info)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 722, in addUdevDevice
    device = self.addUdevLVDevice(info)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 1701, in _populate
    self.addUdevDevice(dev)
  File "/usr/lib/python3.5/site-packages/blivet/populator.py", line 1638, in populate
    self._populate()
  File "/usr/lib/python3.5/site-packages/blivet/devicetree.py", line 555, in populate
    self._populator.populate(cleanupOnly=cleanupOnly)
  File "/usr/lib/python3.5/site-packages/blivet/blivet.py", line 279, in reset
    self.devicetree.populate(cleanupOnly=cleanupOnly)
  File "/usr/lib/python3.5/site-packages/blivet/osinstall.py", line 1157, in storageInitialize
    storage.reset()
  File "/usr/lib64/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.5/site-packages/pyanaconda/threads.py", line 253, in run
    threading.Thread.run(self, *args, **kwargs)
gi.overrides.BlockDev.LVMError: Process reported exit code 1280:   Multiple VGs found with the same name: skipping fedora
  Use the VG UUID with --select vg_uuid=<uuid>


Additional info:
addons:         com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-24 quiet
dnf.rpm.log:    May 02 22:55:17 INFO --- logging initialized ---
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.5.2-302.fc24.x86_64
product:        Fedora
release:        Cannot get release name.
reproducible:   Not sure how to reproduce the problem
type:           anaconda
version:        24

Comment 1 Adam Williamson 2016-05-02 22:57:20 UTC
Created attachment 1153047 [details]
File: anaconda-tb

Comment 2 Adam Williamson 2016-05-02 22:57:21 UTC
Created attachment 1153048 [details]
File: anaconda.log

Comment 3 Adam Williamson 2016-05-02 22:57:22 UTC
Created attachment 1153049 [details]
File: dnf.log

Comment 4 Adam Williamson 2016-05-02 22:57:24 UTC
Created attachment 1153050 [details]
File: environ

Comment 5 Adam Williamson 2016-05-02 22:57:25 UTC
Created attachment 1153051 [details]
File: lsblk_output

Comment 6 Adam Williamson 2016-05-02 22:57:26 UTC
Created attachment 1153052 [details]
File: lvm.log

Comment 7 Adam Williamson 2016-05-02 22:57:27 UTC
Created attachment 1153053 [details]
File: nmcli_dev_list

Comment 8 Adam Williamson 2016-05-02 22:57:28 UTC
Created attachment 1153054 [details]
File: os_info

Comment 9 Adam Williamson 2016-05-02 22:57:30 UTC
Created attachment 1153055 [details]
File: program.log

Comment 10 Adam Williamson 2016-05-02 22:57:32 UTC
Created attachment 1153056 [details]
File: storage.log

Comment 11 Adam Williamson 2016-05-02 22:57:33 UTC
Created attachment 1153057 [details]
File: syslog

Comment 12 Adam Williamson 2016-05-02 22:57:35 UTC
Created attachment 1153058 [details]
File: ifcfg.log

Comment 13 Adam Williamson 2016-05-02 22:57:36 UTC
Created attachment 1153059 [details]
File: packaging.log

Comment 14 Adam Williamson 2016-05-02 23:00:55 UTC
Created attachment 1153060 [details]
lvdisplay output

Going by the lvdisplay output (attached) it's somehow finding the fedora VG I created the *previous* time I ran fw RAID install tests, for F23 Final - even though, before the first F24 Beta install, I went into the Intel RAID firmware interface and destroyed the RAID set! That first install showed the RAID set as empty, as I would expect...but then when I tried to install over it, it's finding both the 'fedora' VG from the install I just ran *and* the 'fedora' VG from the old install before I destroyed and re-created the volume...

Comment 15 Fedora End Of Life 2017-07-25 20:39:28 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 16 Fedora End Of Life 2017-08-08 14:23:41 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.