Bug 1384796
Summary: | udisk does not clean the mount point during reboot | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Lukas Herbolt <lherbolt> |
Component: | udisks2 | Assignee: | Vojtech Trefny <vtrefny> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | bmilar, jkoten, jreznik, tpelka, tsmetana, xhe |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | udisks2-2.7.3-6 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 15:43:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1420851 |
Description
Lukas Herbolt
2016-10-14 07:51:44 UTC
Works fine with labeled disks. But with not labeled disks, UUID is used to create the mount point. UUID mount points still act incorrectly as described earlier: - New directory is created on every reboot /media/<DISKNAME>N where DISKNAME is mounted and the previous old mountpoint remains empty (/media/<DISKNAME>). Tested on x86_64, aarch64, ppc64 with udisks2-2.7.3-4.el7 using image file as a loop device. Test case updated to cover both - labeled and non-labeled partitions - and to be applicable also on remote systems (to test secondary archs). Tested on x86_64, ppc64, ppc64le, aarch64. Bug reproduced with udisks2-2.7.3-4 (for non-labeled partitions). NOT reproduced with udisks2-2.7.3-6. Fix verified. 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-2018:0868 |