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.
Bug 1408572 - tmpfs not mounted to /tmp
Summary: tmpfs not mounted to /tmp
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: releng
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lubos Kocman
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-25 07:25 UTC by Sergey Safarov
Modified: 2017-08-01 17:32 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 17:32:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
tmp mount info (1.39 KB, text/plain)
2017-01-02 13:47 UTC, Sergey Safarov 		no flags Details
tmp mount info 2 (2.62 KB, text/plain)
2017-01-02 18:00 UTC, Sergey Safarov 		no flags Details
boot log (1.40 MB, text/plain)
2017-01-04 14:27 UTC, Sergey Safarov 		no flags Details
Proposed patch (1.35 KB, patch)
2017-01-05 15:51 UTC, Michal Sekletar 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1850 0 normal SHIPPED_LIVE redhat-release update 2017-08-01 18:03:01 UTC

Description Sergey Safarov 2016-12-25 07:25:41 UTC 
Description of problem:
I created fstab file

[root@ip-172-31-39-209 ~]# cat /etc/fstab 
UUID=ef6ba050-6cdc-416a-9380-c14304d0d206 /                       xfs     defaults        0 0
tmpfs	/tmp    tmpfs   size=256m    0 0

After reboot tmpfs not mounted to /tmp path.
If i give command "mount /tmp" then executed correctly

If i change "/tmp" to "/tmp2" and will create "/tmp2 folder, then all will be correct.


Expected results:

After reboot correctly mounted /tmp volume.
Comment 2 Lukáš Nykrýn 2017-01-02 12:31:43 UTC 
What is your version of systemd?

Works just fine on my machine:

[0 root@qeos-225 ~]# mount | grep '/tmp'
tmpfs on /tmp type tmpfs (rw,relatime,seclabel,size=262144k)
[0 root@qeos-225 ~]# grep '/tmp' /etc/fstab
tmpfs	/tmp    tmpfs   size=256m    0 0
[0 root@qeos-225 ~]# rpm -q systemd
systemd-219-30.el7.x86_64

Also could you attach output of "systemctl show tmp.mount"?
Comment 3 Sergey Safarov 2017-01-02 13:46:50 UTC 
Requested info in attached file.
Comment 4 Sergey Safarov 2017-01-02 13:47:46 UTC 
Created attachment 1236663 [details]
tmp mount info
Comment 5 Lukáš Nykrýn 2017-01-02 14:16:51 UTC 
hmmm weird.
Can you check that /run/systemd/generator/tmp.mount and /run/systemd/generator/local-fs.target.requires/tmp.mount exist?
What about "systemctl show local-fs.target"?
Comment 6 Sergey Safarov 2017-01-02 18:00:45 UTC 
Created attachment 1236701 [details]
tmp mount info 2

Requested info is attached in file tmp-mount-info2.txt
Comment 7 Lukáš Nykrýn 2017-01-03 08:41:14 UTC 
Hmm that seems to be fine. Can you try to reboot your machine, put the word "debug" on kernel cmdline and post here the output of "journalctl -b" after the machine boots up?
Comment 8 Sergey Safarov 2017-01-04 14:27:52 UTC 
Created attachment 1237190 [details]
boot log

Requested boot log in attached file "boot-debug.txt"
Comment 9 Michal Sekletar 2017-01-04 17:37:00 UTC 
I tried this with unmodified CentOS7 vagrant box (except updated systemd) and I couldn't reproduce. From logs I can see that you are running the VM machine in EC2. I'd bet that there is something fishy with how that centos7 AMI is built. I'll be able to test this on EC2 tomorrow.
Comment 10 Michal Sekletar 2017-01-05 12:47:33 UTC 
I was able to reproduce this problem on EC2 with both RHEL7 and CentOS7. In both images tmp.mount is masked by default, hence mount unit generated from fstab doesn't take any effect. 

This is a configuration issue and not a bug in systemd. We should talk to people building those AMIs and advice them to stop masking tmp.mount. In the meantime please unmask the unit manually in your provisioning scripts.
Comment 11 Michal Sekletar 2017-01-05 15:51:39 UTC 
Created attachment 1237723 [details]
Proposed patch
Comment 12 Lubos Kocman 2017-01-24 13:04:28 UTC 
Modified in spin-kickstarts

dhcp-24-203:rhel7 lkocman$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

	modified:   rhel-7.3-server-ec2.ks
	modified:   rhel-7.3-server-kvm.ks
	new file:   rhel-7.4-server-ec2.ks
	modified:   rhel-7.4-server-kvm.ks
	modified:   rhel-7.4-server-rt.ks

Change should be visible on next spin of image.

Lubos
Comment 15 errata-xmlrpc 2017-08-01 17:32:24 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://access.redhat.com/errata/RHBA-2017:1850
Note You need to log in before you can comment on or make changes to this bug.