RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1322439 - FSError: umount failed
Summary: FSError: umount failed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-blivet
Version: 7.3
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vojtech Trefny
QA Contact: Release Test Team
URL:
Whiteboard: abrt_hash:a107347e24cea2403aa4e29b6f5...
: 1360228 1371854 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-30 13:53 UTC by Jiri Konecny
Modified: 2021-09-03 14:09 UTC (History)
12 users (show)

Fixed In Version: python-blivet-0.61.15.60-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 23:12:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb (195.06 KB, text/plain)
2016-03-30 13:53 UTC, Jiri Konecny
no flags Details
File: anaconda.log (4.44 KB, text/plain)
2016-03-30 13:53 UTC, Jiri Konecny
no flags Details
File: environ (492 bytes, text/plain)
2016-03-30 13:53 UTC, Jiri Konecny
no flags Details
File: lsblk_output (2.31 KB, text/plain)
2016-03-30 13:53 UTC, Jiri Konecny
no flags Details
File: nmcli_dev_list (2.53 KB, text/plain)
2016-03-30 13:53 UTC, Jiri Konecny
no flags Details
File: os_info (507 bytes, text/plain)
2016-03-30 13:53 UTC, Jiri Konecny
no flags Details
File: program.log (30.17 KB, text/plain)
2016-03-30 13:53 UTC, Jiri Konecny
no flags Details
File: storage.log (53.67 KB, text/plain)
2016-03-30 13:53 UTC, Jiri Konecny
no flags Details
File: syslog (73.25 KB, text/plain)
2016-03-30 13:53 UTC, Jiri Konecny
no flags Details
File: ifcfg.log (2.16 KB, text/plain)
2016-03-30 13:53 UTC, Jiri Konecny
no flags Details
File: packaging.log (1.81 KB, text/plain)
2016-03-30 13:53 UTC, Jiri Konecny
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2207 0 normal SHIPPED_LIVE python-blivet bug fix and enhancement update 2017-08-01 19:42:30 UTC

Description Jiri Konecny 2016-03-30 13:53:35 UTC
Description of problem:
Anaconda raise exception when booting with dvd.

How reproducible:
Always

Steps to reproduce:
1) Insert dvd to your VM
2) Start installation
3) In welcome screen exception will raise

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

The following was filed automatically by anaconda:
anaconda 21.48.22.61-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 703, in unmount
    raise FSError("umount failed")
  File "/tmp/updates/pyanaconda/image.py", line 215, in opticalInstallMedia
    dev.format.unmount()
  File "/tmp/updates/pyanaconda/packaging/__init__.py", line 994, in _setupInstallDevice
    self.install_device = opticalInstallMedia(storage.devicetree)
  File "/tmp/updates/pyanaconda/packaging/yumpayload.py", line 541, in updateBaseRepo
    url, mirrorlist, sslverify = self._setupInstallDevice(self.storage, checkmount)
  File "/tmp/updates/pyanaconda/packaging/yumpayload.py", line 144, in inner_method
    ret = method(yum_payload, *args, **kwargs)
  File "/tmp/updates/pyanaconda/packaging/__init__.py", line 1269, in _runThread
    payload.updateBaseRepo(fallback=fallback, checkmount=checkmount)
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/tmp/updates/pyanaconda/threads.py", line 227, in run
    threading.Thread.run(self, *args, **kwargs)
FSError: umount failed

Additional info:
addons:         org_fedora_oscap, com_redhat_kdump
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=/test/rhel7/initrd.img resolution=1024x768 nokill inst.stage2=http://cobra02/trees/rhel7 updates=http://cobra02/ks/jk/rhel7_updates.img BOOT_IMAGE=/test/rhel7/vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.10.0-369.el7.x86_64
product:        Red Hat Enterprise Linux 7
release:        Red Hat Enterprise Linux Client release 7.3 Beta (Maipo)
release_type:   pre-release
type:           anaconda
uid:            0
version:        7.3

Comment 1 Jiri Konecny 2016-03-30 13:53:39 UTC
Created attachment 1141759 [details]
File: anaconda-tb

Comment 2 Jiri Konecny 2016-03-30 13:53:41 UTC
Created attachment 1141760 [details]
File: anaconda.log

Comment 3 Jiri Konecny 2016-03-30 13:53:42 UTC
Created attachment 1141761 [details]
File: environ

Comment 4 Jiri Konecny 2016-03-30 13:53:43 UTC
Created attachment 1141762 [details]
File: lsblk_output

Comment 5 Jiri Konecny 2016-03-30 13:53:45 UTC
Created attachment 1141763 [details]
File: nmcli_dev_list

Comment 6 Jiri Konecny 2016-03-30 13:53:46 UTC
Created attachment 1141764 [details]
File: os_info

Comment 7 Jiri Konecny 2016-03-30 13:53:47 UTC
Created attachment 1141765 [details]
File: program.log

Comment 8 Jiri Konecny 2016-03-30 13:53:49 UTC
Created attachment 1141766 [details]
File: storage.log

Comment 9 Jiri Konecny 2016-03-30 13:53:51 UTC
Created attachment 1141767 [details]
File: syslog

Comment 10 Jiri Konecny 2016-03-30 13:53:53 UTC
Created attachment 1141768 [details]
File: ifcfg.log

Comment 11 Jiri Konecny 2016-03-30 13:53:54 UTC
Created attachment 1141769 [details]
File: packaging.log

Comment 13 Brian Lane 2016-05-26 21:46:36 UTC
Have you tried this with a newer nightly? I also note that it look like this is actually a PXE boot with an updates.img. And was it an actual DVD build attached to the VM or just a boot.iso?

Comment 14 Jiri Konecny 2016-05-30 11:52:35 UTC
I must apologize because this error is really badly described. From what I remember (I hope I remember it correctly) the problem happens only if I had DVD in my VM and did a PXE boot (without using this DVD, it was attached only) then this crash appeared.

I tested it on newest version of RHEL 7.3 and I can't reproduce it anymore. So I think it's already fixed by something else.

I'm closing this issue now.

Comment 15 Martin Kolman 2016-07-26 09:43:35 UTC
*** Bug 1360228 has been marked as a duplicate of this bug. ***

Comment 16 Jiri Konecny 2016-07-26 09:50:21 UTC
This issue still exists. I'm reopening this bug with better description from bug 1360228 

----------------
> Tried to do a PXE booted install with repositories on an DVD image mounted via > virtual DVD drive.
> Anaconda crashes upon reaching the Welcome screen.
> Looking at the program.log it looks like the ISO from the virtual DVD drive is > mounted once, 
> but then Anaconda tries to unmount it twice, causing the traceback.
----------------

Thank you for reporting this Martin.

Comment 17 David Lehman 2016-07-31 22:59:11 UTC
We mount the optical media, unmount it, then try to unmount it again. The second umount should not have been attempted because we should have been able to tell at that point that there was nothing to unmount.

13:46:27,301 INFO program: Running... mount -t iso9660 -o ro /dev/sr0 /mnt/install/source
13:46:27,316 DEBUG program: Return code: 0
13:46:27,326 INFO program: Running... umount /mnt/install/source
13:46:27,335 DEBUG program: Return code: 0
13:46:28,003 DEBUG program: Return code: 0
13:46:28,092 INFO program: Running... udevadm settle --timeout=300
13:46:28,112 DEBUG program: Return code: 0
13:46:28,118 INFO program: Running... multipath -c /dev/sr0
13:46:28,132 INFO program: /dev/sr0 is not a valid multipath device path
13:46:28,133 DEBUG program: Return code: 1
13:46:28,134 INFO program: Running... udevadm settle --timeout=300
13:46:28,156 DEBUG program: Return code: 0
13:46:28,156 INFO program: Running... umount /mnt/install/source
13:46:28,164 INFO program: umount: /mnt/install/source: not mounted
13:46:28,164 DEBUG program: Return code: 32

Comment 20 Jan Stodola 2016-09-01 14:14:27 UTC
*** Bug 1371854 has been marked as a duplicate of this bug. ***

Comment 24 errata-xmlrpc 2017-08-01 23:12:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2207


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