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 1031046 - Wrong selinux context on /mnt and /mnt/lost+found
Summary: Wrong selinux context on /mnt and /mnt/lost+found
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ec2-images
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 6.7
Assignee: Joey Boggs
QA Contact: mkovacik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-15 14:24 UTC by Ina Panova
Modified: 2017-05-09 18:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-09 18:30:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ina Panova 2013-11-15 14:24:04 UTC
Description of problem:
On a fresh installed instance I perform restorecon command and it says that /mnt and /mnt/lost+found should have mnt_t instead of file_t label


restorecon reset /mnt context system_u:object_r:file_t:s0->system_u:object_r:mnt_t:s0
restorecon reset /mnt/lost+found context system_u:object_r:file_t:s0->system_u:object_r:mnt_t:s0

Version-Release number of selected component (if applicable):
RHEL-6.5_GA-x86_64-1-Access2 (ami-15c59f7c)

How reproducible:
always

Steps to Reproduce:
1. Launch instance
2. Add an ephemeral device
3. Wait until instance is created
4. Perform restorecon command on the instance

Actual results:
file_t label on /mnt and /mnt/lost+found

Expected results:
mnt_t label on /mnt and /mnt/lost+found

Comment 2 RHEL Program Management 2013-11-18 15:18:07 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 5 Joey Boggs 2017-05-09 18:30:39 UTC
I'm not able to reproduce this on 6.9. It also looks like the default labeling has been updated to reflect mnt_t and lost_found_t as well.

drwx------. root root system_u:object_r:lost_found_t:s0 lost+found
drwxr-xr-x. root root system_u:object_r:mnt_t:s0       mnt

If there are still issues please feel free to reopen this bug.


Note You need to log in before you can comment on or make changes to this bug.