Description of problem: This happened when I run anaconda with inst.repo=hd:vda:/dvd.iso and then tried to remove vda1 in the reclaim dialog. It might be a silly thing to do, but I haven't realized that. I guess anaconda should not offer me such partitions to reclaim when it mounted a package repository out of it, or it should say "no no no, that partition can't be removed, because you have selected it as a package source". Version-Release number of selected component: anaconda-18.29.2 Additional info: libreport version: 2.0.17 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.6-3.fc18.i686 description: :The following was filed automatically by anaconda: :anaconda 18.29.2 exception report :Traceback (most recent call first): : File "/usr/lib/python2.7/site-packages/pyanaconda/isys/__init__.py", line 152, in umount : rc = _isys.umount(what) : File "/usr/lib/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 656, in unmount : rc = isys.umount(self._mountpoint, removeDir = False) : File "/usr/lib/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 863, in teardown : return self.unmount(*args, **kwargs) : File "/usr/lib/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 487, in __init__ : device.format.teardown() : File "/usr/lib/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1204, in destroyDevice : self.devicetree.registerAction(ActionDestroyFormat(device)) : File "/usr/lib/python2.7/site-packages/pyanaconda/storage/__init__.py", line 779, in recursiveRemove : self.destroyDevice(device) : File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 261, in _scheduleActions : self.storage.recursiveRemove(device) :SystemError: (32, 'umount: /run/install/isodir: target is busy.\n (In some cases useful info about processes that use\n the device is found by lsof(8) or fuser(1))')
Created attachment 654895 [details] File: anaconda-tb
Created attachment 654896 [details] File: product
Created attachment 654897 [details] File: type
Created attachment 654898 [details] File: ifcfg.log
Created attachment 654899 [details] File: storage.log
Created attachment 654900 [details] File: version
Created attachment 654901 [details] File: environ
Created attachment 654902 [details] File: executable
Created attachment 654903 [details] File: anaconda.log
Created attachment 654904 [details] File: syslog
Created attachment 654905 [details] File: hashmarkername
Created attachment 654906 [details] File: packaging.log
Created attachment 654907 [details] File: cmdline_file
Created attachment 654908 [details] File: release
Created attachment 654909 [details] File: program.log
I guess this hits: " Rejecting obviously invalid operations without crashing " https://fedoraproject.org/wiki/Fedora_18_Beta_Release_Criteria But it is a very specific use case, I wonder whether we want to block on that. In ideal world yes, in reality I'm not so sure.
When I was careful not to remove vda1, I ended up with bug 879610 comment 18.
Discussed at 2012-12-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-12-03/f18final-blocker-review-1.2.2012-12-03-17.25.log.txt . Rejected as a blocker - this is borderline, but we're fairly sure we ultimately wouldn't block for such a 'doctor, it hurts' problem. Accepted as NTH, it's a crasher in install.
pykickstart-1.99.22-1.fc18, anaconda-18.35-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2012-19380/pykickstart-1.99.22-1.fc18,anaconda-18.35-1.fc18
Package pykickstart-1.99.22-1.fc18, anaconda-18.35-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing pykickstart-1.99.22-1.fc18 anaconda-18.35-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19380/pykickstart-1.99.22-1.fc18,anaconda-18.35-1.fc18 then log in and leave karma (feedback).
pykickstart-1.99.22-1.fc18, anaconda-18.35-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Reopening. If I open the reclaim dialog twice, I can still remove hdiso source partition. See bug 853789 comment 16 and 17.
Also see bug 884599, which is the same problem, just with manual partitioning screen.
anaconda-18.37-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.37-1.fc18
Package anaconda-18.37-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.37-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19991/anaconda-18.37-1.fc18 then log in and leave karma (feedback).
The problem mentioned in comment 22 is fixed in anaconda 18.37. Setting as verified.
anaconda-18.37.2-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.