Bug 1040962

Summary: LVMError: lvactivate failed for home: running lvm lvchange -a y --config devices { filter=["r|/sdd1$|","r|/sdd2$|","r|/sdd3$|","r|/sdc1$|","r|/sdc$|"] } fedora_dhcp-28-168/home failed
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
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: 20CC: anaconda-maint-list, g.kaviyarasu, joe, jonathan, vanmeeuwen+fedora, vibha0606
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5a7141a9f5506c0e185c56905c6e051f0c171bb7461eaf67f060c93bc20b7870
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:29:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: environ
none
File: lsblk_output
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

Description Kamil Páral 2013-12-12 12:28:30 UTC
Description of problem:
I think I did the following:
1. install default LVM install to /dev/sdb and /dev/sdc
2. boot into installer again
3. install default LVM layout to /dev/sda and /dev/sdb. Remove the previous partitions first. The new VG is named the same way as the old VG.

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

The following was filed automatically by anaconda:
anaconda 20.25.15-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 437, in lvactivate
    raise LVMError("lvactivate failed for %s: %s" % (lv_name, msg))
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2682, in _setup
    lvm.lvactivate(self.vg.name, self._name)
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 716, in setup
    self._setup(orig=orig)
  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 534, in execute
    self.device.setup(orig=True)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 239, in processActions
    action.execute()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 308, in doIt
    self.devicetree.processActions()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 167, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 142, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall)
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 192, in run
    threading.Thread.run(self, *args, **kwargs)
LVMError: lvactivate failed for home: running lvm lvchange -a y --config  devices { filter=["r|/sdd1$|","r|/sdd2$|","r|/sdd3$|","r|/sdc1$|","r|/sdc$|"] }  fedora_dhcp-28-168/home failed

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020\x20x86_64 quiet BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.11.10-301.fc20.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        20

Potential duplicate: bug 950173

Comment 1 Kamil Páral 2013-12-12 12:28:36 UTC
Created attachment 835771 [details]
File: anaconda-tb

Comment 2 Kamil Páral 2013-12-12 12:28:38 UTC
Created attachment 835772 [details]
File: anaconda.log

Comment 3 Kamil Páral 2013-12-12 12:28:40 UTC
Created attachment 835773 [details]
File: environ

Comment 4 Kamil Páral 2013-12-12 12:28:42 UTC
Created attachment 835774 [details]
File: lsblk_output

Comment 5 Kamil Páral 2013-12-12 12:28:44 UTC
Created attachment 835775 [details]
File: nmcli_dev_list

Comment 6 Kamil Páral 2013-12-12 12:28:46 UTC
Created attachment 835776 [details]
File: os_info

Comment 7 Kamil Páral 2013-12-12 12:28:48 UTC
Created attachment 835777 [details]
File: program.log

Comment 8 Kamil Páral 2013-12-12 12:28:51 UTC
Created attachment 835778 [details]
File: storage.log

Comment 9 Kamil Páral 2013-12-12 12:28:53 UTC
Created attachment 835779 [details]
File: syslog

Comment 10 Kamil Páral 2013-12-12 12:28:55 UTC
Created attachment 835780 [details]
File: ifcfg.log

Comment 11 Kamil Páral 2013-12-12 12:28:58 UTC
Created attachment 835781 [details]
File: packaging.log

Comment 12 Kamil Páral 2013-12-12 13:12:03 UTC
I can't reproduce this.

Comment 13 Joseph D. Wagner 2014-04-04 14:43:11 UTC
I was able to reproduce it with my configuration.  The important part appears to be a luks & lvm partition which you don't reformat.  In this case, I didn't want to reformat /home.

NAME                                          MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
sda                                             8:0    0  3.7T  0 disk  
├─sda1                                          8:1    0 1023M  0 part  /boot/efi
├─sda2                                          8:2    0  192G  0 part  
├─sda3                                          8:3    0  512M  0 part  /boot
└─sda4                                          8:4    0  3.5T  0 part  
  └─luks-0daf88bc-af22-4a25-8375-0aa9c867a61a 253:0    0  3.5T  0 crypt 
    ├─system-swap                             253:1    0   16G  0 lvm   [SWAP]
    └─system-os                               253:2    0  512G  0 lvm   /
sdb                                             8:16   0  3.7T  0 disk  
└─sdb1                                          8:17   0  3.7T  0 part  
  └─luks-bc1e37d2-243b-4f9b-91d0-f8fa0632a0ca 253:3    0  3.7T  0 crypt 
    └─data-home                               253:4    0    2T  0 lvm   /home
sdc                                             8:32   0  1.8T  0 disk  
└─sdc1                                          8:33   0  1.8T  0 part  
sr0                                            11:0    1 1024M  0 rom

Comment 14 Fedora End Of Life 2015-05-29 09:58:27 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 15 Fedora End Of Life 2015-06-29 13:29:19 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.