Bug 1298109

Summary: tmpfs is unexpectedly mounted on /tmp in rhel-7
Product: Red Hat Enterprise Linux 7 Reporter: Mohit Agrawal <moagrawa>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Branislav Blaškovič <bblaskov>
Severity: high Docs Contact:
Priority: high    
Version: 7.3CC: bblaskov, ealcaniz, gerwinkrist, jaeshin, lnykryn, rcernin, salmy, systemd-maint-list
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-219-20.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1298209 (view as bug list) Environment:
Last Closed: 2016-11-04 00:50:26 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: 1298209, 1339488    

Description Mohit Agrawal 2016-01-13 09:21:22 UTC
Description of problem:
tmpfs is unexpectedly mounted on /tmp when user start any unit file that configured PrivateTmp=true


Version-Release number of selected component (if applicable):
systemd-219-19.el7.x86_64

How reproducible:
Always
Steps to Reproduce:
1) df /tmp
 df /tmp
Filesystem                            1K-blocks     Used Available Use% Mounted on
/dev/mapper/rhel_dell--per630--2-root  52403200 19977388  32425812  39% /

2 ) systemctl status tmp.mount; 

But after start systemd-timedated it is start automatically and created mount-point.
3 ) systemctl start systemd-timedated; 
4) df /tmp
Filesystem     1K-blocks  Used Available Use% Mounted on
tmpfs            8010868     0   8010868   0% /tmp



Actual results:
/tmp is created new mount point on tmpfs

Expected results:
mount point should not create automatically.

Additional info:

Comment 3 Lukáš Nykrýn 2016-01-13 09:49:41 UTC
Just a small note, workaround for this issue is to mask the tmp.mount by calling:

systemctl mask tmp.mount

Comment 13 errata-xmlrpc 2016-11-04 00:50:26 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://rhn.redhat.com/errata/RHBA-2016-2216.html