Bug 1647714
| Summary: | /etc/selinux/fixfiles_exclude_dirs and /etc/selinux//targeted/contexts/files/file_contexts.local | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Franky Van Liedekerke <franky> | |
| Component: | policycoreutils | Assignee: | Vit Mojzis <vmojzis> | |
| Status: | CLOSED ERRATA | QA Contact: | Jan Zarsky <jzarsky> | |
| Severity: | medium | Docs Contact: | Mirek Jahoda <mjahoda> | |
| Priority: | high | |||
| Version: | 7.6 | CC: | dwalsh, fkrska, jzarsky, lvrabec, mjahoda, mmalik, plautrba, ssekidde, zpytela | |
| Target Milestone: | rc | Keywords: | Regression, ZStream | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
.`fixfiles` no longer incorrectly fails
Previously, the `fixfiles` script failed if the `/etc/selinux/fixfiles_exclude_dirs` file contained at least one entry and the `/etc/selinux/targeted/contexts/files/file_contexts.local` file was not present. With this update, the requirement for existence of `/etc/selinux/targeted/contexts/files/file_contexts.local` has been removed, and fixfiles now works correctly in the described scenario.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1665813 (view as bug list) | Environment: | ||
| Last Closed: | 2019-08-06 13:00:15 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1665813 | |||
|
Description
Franky Van Liedekerke
2018-11-08 08:22:53 UTC
Thank you for reporting the issue. We are working on a resolution. 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-2019:2160 |