Bug 1402006 - semanage fcontext -m returns "OSError: No such file or directory" and fails to alter contexts
Summary: semanage fcontext -m returns "OSError: No such file or directory" and fails t...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: policycoreutils
Version: 7.3
Hardware: All
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Petr Lautrbach
QA Contact: Milos Malik
Mirek Jahoda
URL:
Whiteboard:
Depends On: 1398427
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-06 14:49 UTC by Marcel Kolaja
Modified: 2020-02-14 18:15 UTC (History)
11 users (show)

Fixed In Version: policycoreutils-2.5-11.el7_3
Doc Type: Bug Fix
Doc Text:
Previously, the "semanage fcontext -m" operation returned "OSError: No such file or directory" and failed to modify the target file context. A patch has been applied, and the exception is handled correctly. As a result, it is possible to modify the file context with the "semanage fcontext -m" command.
Clone Of: 1398427
Environment:
Last Closed: 2017-01-17 18:09:22 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2779831 0 None None None 2016-12-06 14:49:12 UTC
Red Hat Product Errata RHBA-2017:0075 0 normal SHIPPED_LIVE libsemanage and policycoreutils bug fix update 2017-01-17 22:51:04 UTC

Description Marcel Kolaja 2016-12-06 14:49:02 UTC 
This bug has been copied from bug #1398427 and has been proposed
to be backported to 7.3 z-stream (EUS).
Comment 12 errata-xmlrpc 2017-01-17 18:09:22 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-2017-0075.html
Note You need to log in before you can comment on or make changes to this bug.