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 1410733 - fixfiles does not repair SELinux contexts in paths which contain at least 1 space
Summary: fixfiles does not repair SELinux contexts in paths which contain at least 1 s...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: policycoreutils
Version: 6.9
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Petr Lautrbach
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-06 09:39 UTC by Milos Malik
Modified: 2019-06-05 07:32 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1717319 (view as bug list)
Environment:
Last Closed: 2017-07-17 08:06:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Milos Malik 2017-01-06 09:39:47 UTC 
Description of problem:
* the problem appears if you run fixfiles on a path which contains at least 1 space

Version-Release number of selected component (if applicable):
policycoreutils-2.0.83-30.1.el6_8.x86_64

How reproducible:
* always

Steps to Reproduce:
# mkdir space\ in\ the\ name
# s -dZ space\ in\ the\ name
drwxr-xr-x. root root unconfined_u:object_r:admin_home_t:s0 space in the name
# chcon -t tmp_t space\ in\ the\ name
# ls -dZ space\ in\ the\ name
drwxr-xr-x. root root unconfined_u:object_r:tmp_t:s0   space in the name
# fixfiles restore ./space\ in\ the\ name
/sbin/restorecon:  lstat(./space) failed:  No such file or directory
/sbin/restorecon:  lstat(in) failed:  No such file or directory
/sbin/restorecon:  lstat(the) failed:  No such file or directory
/sbin/restorecon:  lstat(name) failed:  No such file or directory
# ls -dZ space\ in\ the\ name
drwxr-xr-x. root root unconfined_u:object_r:tmp_t:s0   space in the name
# restorecon -Rv /root
restorecon reset /root/space in the name context unconfined_u:object_r:tmp_t:s0->unconfined_u:object_r:admin_home_t:s0
#

Actual results:
* files/directories with spaces in their names are skipped

Expected results:
* files/directories with spaces in their names are handled correctly
Comment 2 Petr Lautrbach 2017-01-06 10:12:36 UTC 
Is this considered a high severity issue? If not, it doesn't meet Production phase 2 criteria and I will have to close it.
Comment 3 Milos Malik 2017-07-17 08:05:01 UTC 
This is not a high severity issue.
Note You need to log in before you can comment on or make changes to this bug.