Bug 1197036
| Summary: | No context defined for mongos binary and initscript | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Honza Horak <hhorak> | |
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> | |
| Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.7 | CC: | bgollahe, dwalsh, jsvarova, lvrabec, mgrepl, mmalik, plautrba, pvrabec, ssekidde | |
| Target Milestone: | rc | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | selinux-policy-3.7.19-262.el6 | Doc Type: | Bug Fix | |
| Doc Text: |
Prior to this update, the mongos binary and the mongos SysV init scripts did not have the SELinux context defined. This update fixes the bug by adding the respective SELinux context.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1197038 1212971 1212972 (view as bug list) | Environment: | ||
| Last Closed: | 2015-07-22 07:11:35 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: | 1197038, 1212373, 1212971, 1212972 | |||
|
Description
Honza Horak
2015-02-27 11:28:23 UTC
mongos deamon and initscript is available only in mongodb-2.6 and later. Reason why we'd like to have those context in RHEL-6 even if there is no mongodb-2.6 in epel-6 is that we're about to ship rh-mongodb26 Software Collection, that defines equivalence: semange fcontext -a -e /etc/rc.d/init.d/mongos /etc/rc.d/init.d/rh-mongodb26-mongos commit 8005531f1ffbfc2a107445cab1c1d01bacc8c8e7
Author: Miroslav Grepl <mgrepl>
Date: Wed Mar 4 14:26:24 2015 +0100
Add support for mongos service.
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-2015-1375.html |