Bug 1105313

Summary: [RHEL7.0 PREUPGRADE] New /run partition conflicts with existing /run partitions
Product: Red Hat Enterprise Linux 6 Reporter: Matt Ruzicka <mruzicka>
Component: preupgrade-assistant-contentsAssignee: Petr Stodulka <pstodulk>
Status: CLOSED ERRATA QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.5CC: fkluknav, jkurik, ovasik, phracek, pstodulk, ttomecek
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-14 10:19:23 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: 1044717    

Description Matt Ruzicka 2014-06-05 20:39:45 UTC
Description of problem:

Customer with a very large infrastructure utilizes /run as a working file system (as their system has been migrated from Business Basic from many years back).  Rhel 7's new /run tmpfs conflicts with their existing file structure.

We don't expect /run to be changed in RHEL 7, but it seems the pre-upgrade assistant should detect this as a fail and the RHEL release notes and general documentation should probably make more obvious note of /run being reclaimed for system use.

Version-Release number of selected component (if applicable):

RHEL 6.5 to RHEL 7 in place upgrade using:

# rpm -qa|grep upgrade
redhat-upgrade-tool-0.7.6-1.el7.noarch
preupgrade-assistant-1.0.2-18.el6.x86_64
preupgrade-assistant-contents-0.5.3-1.el6.noarch

How reproducible:

Always. When RHEL 6.5 is upgraded to RHEL 7 or RHEL 7 is installed new, system tmpfs /run partition exists and conflicts with their normal use of /run

Additional Notes:

part of RH Case #01115323

Comment 2 Matt Ruzicka 2014-06-05 21:05:48 UTC
Looks like there was more information provided when this came down in Fedora.

http://docs.fedoraproject.org/en-US/Fedora/15/html/Release_Notes/sect-Release_Notes-Changes_for_SysAdmin.html

3.2.2. /run directory
Fedora 15 has a /run directory for storing runtime data. /run is now a tmpfs, and /var/run is bind mounted to it. /var/lock is bind mounted to /run/lock. Applications can use /run the same way as /var/run. Several programs including udev, dracut, mdadm, mount and initscripts used hidden directories under /dev for runtime data during early bootup before /var is mounted. However /dev/ is supposed to be used for only device nodes and there is consensus between major distributions to shift to using /run instead. Fedora 15 is leading this change. Details including the benefits are explained here.
This change is compliant with the Filesystem Hierarchy Standard, which allows distributions to create new directories in the root hierarchy as long as there is careful consideration of the consequences. Co-author of the latest FHS specification has expressed support for this change. Lennart Poettering has filed a request to update the FHS standard to include this change as well.

3.2.3. /var/run and /var/lock
/var/run and /var/lock are now bind mounted to /run and /run/lock from tmpfs, and hence emptied on reboot. Applications must ensure to recreate their own files/dirs on startup, and cannot rely that doing this at package installation will suffice. It is possible to use systemd's tmpfiles.d mechanism to recreate directories and files beneath /var/run and /var/lock on boot, if necessary. See tmpfiles.d(5) for details (http://0pointer.de/public/systemd-man/tmpfiles.d.html) and the conf files in /etc/tmpfiles.d for examples of such configuration. Fedora packaging guidelines for tmpfiles.d is at http://fedoraproject.org/wiki/Packaging:Tmpfiles.d.

Comment 8 Petr Stodulka 2014-07-03 12:36:21 UTC
Modul prepared for check.
RHEL6_7/system/RunFHS

Comment 14 errata-xmlrpc 2014-10-14 10:19:23 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.

http://rhn.redhat.com/errata/RHBA-2014-1627.html