Bug 950173 - LVMError: lvactivate failed for swap: running lvm lvchange -a y --config devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] } fedora/swap failed
Summary: LVMError: lvactivate failed for swap: running lvm lvchange -a y --config dev...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5a7141a9f5506c0e185c56905c6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-09 19:22 UTC by Adam Williamson
Modified: 2014-02-28 17:39 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-28 17:39:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb (992.01 KB, text/plain)
2013-04-09 19:22 UTC, Adam Williamson
no flags Details
File: anaconda.log (32.96 KB, text/plain)
2013-04-09 19:22 UTC, Adam Williamson
no flags Details
File: backtrace (1.43 KB, text/plain)
2013-04-09 19:22 UTC, Adam Williamson
no flags Details
File: environ (780 bytes, text/plain)
2013-04-09 19:22 UTC, Adam Williamson
no flags Details
File: ifcfg.log (486 bytes, text/plain)
2013-04-09 19:23 UTC, Adam Williamson
no flags Details
File: lsblk_output (1.62 KB, text/plain)
2013-04-09 19:23 UTC, Adam Williamson
no flags Details
File: nmcli_dev_list (3.31 KB, text/plain)
2013-04-09 19:23 UTC, Adam Williamson
no flags Details
File: packaging.log (611.99 KB, text/plain)
2013-04-09 19:23 UTC, Adam Williamson
no flags Details
File: program.log (35.17 KB, text/plain)
2013-04-09 19:23 UTC, Adam Williamson
no flags Details
File: storage.log (197.56 KB, text/plain)
2013-04-09 19:23 UTC, Adam Williamson
no flags Details
File: syslog (73.00 KB, text/plain)
2013-04-09 19:23 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2013-04-09 19:22:34 UTC
Description of problem:
Installing F19 Alpha RC1 to a VM with two virtio disks, with /boot and swap as ext4 partitions and / as a software RAID-0 array, configured via custom partitioning.
The following was filed automatically by anaconda:
anaconda 19.16-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 385, in lvactivate
    raise LVMError("lvactivate failed for %s: %s" % (lv_name, msg))
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2539, in _setup
    lvm.lvactivate(self.vg.name, self._name)
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 717, in setup
    self._setup(orig=orig)
  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 526, in execute
    self.device.setup(orig=True)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 241, in processActions
    action.execute()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 298, in doIt
    self.devicetree.processActions()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 157, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 119, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall)
  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 141, in run
    threading.Thread.run(self, *args, **kwargs)
LVMError: lvactivate failed for swap: running lvm lvchange -a y --config  devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] }  fedora/swap failed

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

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019-Alpha\x20x86_64 quiet slub_debug=- BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.9.0-0.rc4.git0.1.fc19.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        19-Alpha

Truncated backtrace:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run
    threading.Thread.run(self, *args, **kwargs)
  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/install.py", line 119, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 157, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 298, in doIt
    self.devicetree.processActions()
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 241, in processActions
    action.execute()
  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 526, in execute
    self.device.setup(orig=True)
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 717, in setup
    self._setup(orig=orig)
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2539, in _setup
    lvm.lvactivate(self.vg.name, self._name)
  File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 385, in lvactivate
    raise LVMError("lvactivate failed for %s: %s" % (lv_name, msg))
LVMError: lvactivate failed for swap: running lvm lvchange -a y --config  devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] }  fedora/swap failed

Comment 1 Adam Williamson 2013-04-09 19:22:46 UTC
Created attachment 733337 [details]
File: anaconda-tb

Comment 2 Adam Williamson 2013-04-09 19:22:52 UTC
Created attachment 733338 [details]
File: anaconda.log

Comment 3 Adam Williamson 2013-04-09 19:22:56 UTC
Created attachment 733339 [details]
File: backtrace

Comment 4 Adam Williamson 2013-04-09 19:22:58 UTC
Created attachment 733340 [details]
File: environ

Comment 5 Adam Williamson 2013-04-09 19:23:00 UTC
Created attachment 733341 [details]
File: ifcfg.log

Comment 6 Adam Williamson 2013-04-09 19:23:02 UTC
Created attachment 733342 [details]
File: lsblk_output

Comment 7 Adam Williamson 2013-04-09 19:23:04 UTC
Created attachment 733343 [details]
File: nmcli_dev_list

Comment 8 Adam Williamson 2013-04-09 19:23:10 UTC
Created attachment 733344 [details]
File: packaging.log

Comment 9 Adam Williamson 2013-04-09 19:23:20 UTC
Created attachment 733345 [details]
File: program.log

Comment 10 Adam Williamson 2013-04-09 19:23:23 UTC
Created attachment 733346 [details]
File: storage.log

Comment 11 Adam Williamson 2013-04-09 19:23:26 UTC
Created attachment 733347 [details]
File: syslog

Comment 12 David Shea 2014-02-28 15:01:53 UTC
What was on the disk to begin with? The problem appears to be with old volume groups. Does it still occur?

Comment 13 Adam Williamson 2014-02-28 17:20:38 UTC
oh, jeez, this is like a year old. you know how many VM installs I run per year, right? :)

if you can't get anywhere from the logs just close it, there's no way I'll be able to reproduce now.

Comment 14 David Shea 2014-02-28 17:39:46 UTC
(In reply to Adam Williamson from comment #13)
> oh, jeez, this is like a year old. you know how many VM installs I run per
> year, right? :)

Guess how many VM installs are in this jar and win a prize

> 
> if you can't get anywhere from the logs just close it, there's no way I'll
> be able to reproduce now.

I just tried recreating what looked like the old LVM setup in the logs and installing the RAID-0 setup you described on top of it with F20, and that worked fine, so let's say this one got fixed.


Note You need to log in before you can comment on or make changes to this bug.