Bug 1337743
| Summary: | Having something mounted on /mnt makes filesystem updated rpm fail to install | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | lindahl |
| Component: | rpm | Assignee: | Florian Festi <ffesti> |
| Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | lindahl |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-09 14:58:12 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: | |||
|
Description
lindahl
2016-05-20 00:45:01 UTC
Thanks for report - definitely worth investigation. Issues with filesystem updates usually happen when something modifies permissions on the affected directory. I'll try to reproduce this based on your steps to reproduce, if not succesful, will ask for more detailed step-by-step description of your reproducer. Can't reproduce on my machine with the provided reproducer... $ mount | grep mnt /mnt/blob on /mnt/mnt type ext2 (ro,relatime,seclabel) and reinstall of the filesystem package just works. Can you please check: 1) rpm -V filesystem 2) provide step by step reproducer (at least more detailed information, so I can find some differences in the scenario... Thanks in advance! ah - I seem to understand now ... you mount things directly to /mnt as readonly ... but this is definitely wrong way - you should have subdir for mounting mounts... If this is the case, filesystem package is innocent here - as you modify the permissions on the /mnt dir owned by filesystem. Therefore, update of filesystem package will fail - but this is not a bug in filesystem package, more flaw in your concept of mounting temporary mounts. Yes, I mounted it on /mnt. This was OK for a few decades, and if you look at google for advice on mounting things loopback, you'll see quite a few examples of mounting directly on /mnt. So sure, not a bug for someone who understands how the filesystem package works. What about the other 99%? Ok, if it was ok for few decades, you can blame rpm for being more strict, as there is no change in the filesystem package /mnt directory ownership in RHEL 7. I'll reassign that to rpm, so they are aware of the impact of "being more strict" about dir conflicts. This caused similar issue with google-maps package in Fedora (as their package is poorly packaged and owns /usr with different permissions than filesystem package). I think this is really NOTABUG, but let's keep it on rpm guys. There is not really a good way to deal with this from an RPM POV. RPM feaking out when not being able to lay down files properly is the right thing IMHO. RPM offers a way to deal with RO mounted parts of the file system in /usr/lib/rpm/macros: # A colon separated list of paths where files should *not* be installed. # Usually, these are network file system mount points. # #%_netsharedpath May be adding /mnt solves this for some use cases. Closing. |