Description of problem: Version-Release number of selected component: anaconda-28.22.10 The following was filed automatically by anaconda: anaconda 28.22.10 exception report Traceback (most recent call first): File "/usr/lib/python3.6/site-packages/blivet/formats/fs.py", line 611, in _teardown raise FSError("umount of %s failed (%d)" % (mountpoint, rc)) File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/formats/__init__.py", line 649, in teardown self._teardown(**kwargs) File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/devices/storage.py", line 412, in _pre_teardown self.original_format.teardown() File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/devices/storage.py", line 426, in teardown if not self._pre_teardown(recursive=recursive): File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock return m(*args, **kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/__init__.py", line 1103, in reset_install_device self.install_device.teardown(recursive=True) File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/__init__.py", line 1092, in reset self.reset_install_device() File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/dnfpayload.py", line 1019, in reset super().reset() File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/dnfpayload.py", line 1029, in updateBaseRepo self.reset() File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/__init__.py", line 1658, in _runThread payload.updateBaseRepo(fallback=fallback, checkmount=checkmount) File "/usr/lib64/python3.6/threading.py", line 864, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 291, in run threading.Thread.run(self) blivet.errors.FSError: umount of /run/install/source failed (32) Additional info: addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 rd.live.check quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.16.3-301.fc28.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 28
Created attachment 1440767 [details] File: anaconda-tb
Created attachment 1440768 [details] File: anaconda.log
Created attachment 1440769 [details] File: dbus.log
Created attachment 1440770 [details] File: dnf.librepo.log
Created attachment 1440771 [details] File: environ
Created attachment 1440772 [details] File: hawkey.log
Created attachment 1440773 [details] File: lorax-packages.log
Created attachment 1440774 [details] File: lsblk_output
Created attachment 1440775 [details] File: lvm.log
Created attachment 1440776 [details] File: nmcli_dev_list
Created attachment 1440777 [details] File: os_info
Created attachment 1440778 [details] File: program.log
Created attachment 1440779 [details] File: storage.log
Created attachment 1440780 [details] File: syslog
Created attachment 1440781 [details] File: ifcfg.log
Created attachment 1440782 [details] File: packaging.log
Based on the traceback I'm switching this to our storage library.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.