Description of problem: I used anaconda from comandline to install to image file (anaconda --image=test.img). At the end of the installation there is button for Reboot, instead of Quit. So I clicked reboot and than the anaconda fell. Version-Release number of selected component: anaconda-core-21.39-1.fc21.x86_64 The following was filed automatically by anaconda: anaconda 21.39-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 686, in _setName raise errors.DeviceError("Cannot rename existing device.") File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 406, in <lambda> lambda s, v: s._setName(v), File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 4253, in _postTeardown self.name = "tmploop%d" % self.id File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 870, in teardown self._postTeardown(recursive=recursive) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 365, in teardownParents parent.teardown(recursive=recursive) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 875, in _postTeardown self.teardownParents(recursive=recursive) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 870, in teardown self._postTeardown(recursive=recursive) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2108, in deactivate StorageDevice.teardown(self, recursive=recursive) File "/sbin/anaconda", line 79, in exitHandler dev.deactivate(recursive=True) File "/usr/lib64/python2.7/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) DeviceError: Cannot rename existing device. Additional info: cmdline: /usr/bin/python /sbin/anaconda --image=test.img cmdline_file: BOOT_IMAGE=/vmlinuz-3.15.0-0.rc7.git4.2.fc21.x86_64 root=UUID=3c3dedd5-e971-4ac4-96dd-aa3ac3c61882 ro rd.lvm.lv=main/root rd.luks.uuid=luks-e9ed0c8b-261b-465a-94f5-5c1e5064eae6 rd.lvm.lv=main/swap rhgb quiet LANG=en_US.UTF-8 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.15.0-0.rc7.git4.2.fc21.x86_64 other involved packages: python-libs-2.7.6-8.fc21.x86_64, python-blivet-0.54-1.fc21.noarch product: Fedora release: Fedora release 21 (Rawhide) type: anaconda version: rawhide
Created attachment 902042 [details] File: anaconda-tb
Created attachment 902043 [details] File: anaconda.log
Created attachment 902044 [details] File: environ
Created attachment 902045 [details] File: journalctl
Created attachment 902046 [details] File: lsblk_output
Created attachment 902047 [details] File: nmcli_dev_list
Created attachment 902048 [details] File: os_info
Created attachment 902049 [details] File: program.log
Created attachment 902050 [details] File: storage.log
Created attachment 902051 [details] File: ifcfg.log
Created attachment 902052 [details] File: packaging.log
*** Bug 1104607 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: Happens on start of liveinst on a current Rawhide-based live image (anaconda 21.39), in a VM with an existing btrfs install of Rawhide on its disk. (That seems to be important). cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=20140604-grubby-x86_64 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.15.0-0.rc8.git1.2.fc21.x86_64 other involved packages: python-libs-2.7.6-9.fc21.x86_64, python-blivet-0.54-1.fc21.noarch package: anaconda-core-21.39-1.fc21.x86_64 packaging.log: product: Fedora reason: DeviceError: Cannot rename existing device. release: Fedora release 21 (Rawhide) version: rawhide
I'm not sure #1104607 is really a dupe of this. Or, at least, they may share the same underlying cause - dlehman mentions in passing "the places where you replaced setting self._name with setting self.name" - but the patch you've posted - https://lists.fedorahosted.org/pipermail/anaconda-patches/2014-June/011389.html - is not sufficient to fix all the resulting bugs. #1104607 happens on *startup* of install when there is an existing btrfs volume on an attached disk (I believe). I don't think it has to do with the name of a loop device during teardown.
*** Bug 1105858 has been marked as a duplicate of this bug. ***
This should be fixed by 67c8140b1c8c210afa2847b9a90866b89982c2f7