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.

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:

Just a small note, workaround for this issue is to mask the tmp.mount by calling:

systemctl mask tmp.mount

https://github.com/lnykryn/systemd-rhel/commit/14eaa63230a16a32f49db74d4b0d78247874ccdd -> post

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