Bug 903412

Summary: installer does not support lvm configurations that include thin provisioning
Product: [Fedora] Fedora Reporter: Charles Butterfield <cb20777>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, g.kaviyarasu, jonathan, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:95e80a56cae6568a26572a2fb1a82945e19bcd933417d287c3bf276f118a4220
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-18 13:49:12 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: environ
none
File: ifcfg.log
none
File: packaging.log
none
File: program.log
none
File: storage.log none

Description Charles Butterfield 2013-01-23 23:04:10 UTC
Description of problem:
Encountered during F18 network install
The following was filed automatically by anaconda:
anaconda 18.37.11 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicelibs/lvm.py", line 401, in lvactivate
    raise LVMError("lvactivate failed for %s: %s" % (lv_name, msg))
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 2542, in _setup
    lvm.lvactivate(self.vg.name, self._name)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 714, in setup
    self._setup(orig=orig)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1305, in handleVgLvs
    lv_device.setup()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1751, in _setupLvs
    if self.handleVgLvs(device):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1939, in _populate
    if self._setupLvs():
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1842, in populate
    self._populate()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 428, in reset
    self.devicetree.populate(cleanupOnly=cleanupOnly)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 147, in storageInitialize
    storage.reset()
  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: lvactivate failed for [pool_tdata]: running lvm lvchange -a y --config  devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] }  g2/[pool_tdata] failed

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018\x20x86_64 quiet BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.6.10-4.fc18.x86_64
other involved packages: 
package:        anaconda-18.37.11
product:        Fedora
release:        Cannot get release name.
type:           libreport
version:        18

Comment 1 Charles Butterfield 2013-01-23 23:04:13 UTC
Created attachment 686332 [details]
File: anaconda-tb

Comment 2 Charles Butterfield 2013-01-23 23:04:15 UTC
Created attachment 686333 [details]
File: anaconda.log

Comment 3 Charles Butterfield 2013-01-23 23:04:17 UTC
Created attachment 686334 [details]
File: environ

Comment 4 Charles Butterfield 2013-01-23 23:04:19 UTC
Created attachment 686335 [details]
File: ifcfg.log

Comment 5 Charles Butterfield 2013-01-23 23:04:21 UTC
Created attachment 686336 [details]
File: packaging.log

Comment 6 Charles Butterfield 2013-01-23 23:04:23 UTC
Created attachment 686337 [details]
File: program.log

Comment 7 Charles Butterfield 2013-01-23 23:04:25 UTC
Created attachment 686338 [details]
File: storage.log

Comment 8 Charles Butterfield 2013-01-23 23:28:50 UTC
This seemed to be caused by the LVM thin pool.  I rebooted the old OS, did lvremove on the thin pool and the LV mounted on it and the network install worked fine thereafter (well at least it has gotten to the downloading packages stage) :-)

Comment 9 Chris Lumens 2013-01-24 15:42:09 UTC
Yeah, we do not yet support thinp.

Comment 10 Fedora End Of Life 2015-01-09 22:03:27 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 11 Fedora End Of Life 2015-02-18 13:49:12 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.