Bug 1609427
| Summary: | ceph-volume does not set SELinux context of newly mounted filesystems | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Boris Ranto <branto> | |
| Component: | Ceph-Volume | Assignee: | Boris Ranto <branto> | |
| Status: | CLOSED ERRATA | QA Contact: | Ramakrishnan Periyasamy <rperiyas> | |
| Severity: | urgent | Docs Contact: | Aron Gunn <agunn> | |
| Priority: | urgent | |||
| Version: | 3.0 | CC: | agunn, branto, ceph-eng-bugs, ceph-qe-bugs, hnallurv, shmohan, tserlin | |
| Target Milestone: | rc | |||
| Target Release: | 3.1 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | RHEL: ceph-12.2.5-37.el7cp Ubuntu: ceph_12.2.5-22redhat1 | Doc Type: | Bug Fix | |
| Doc Text: |
.The SELinux context is set correctly when using `ceph-volume` for new filesystems
The `ceph-volume` utility was not labeling newly created filesystems, which was causing `AVC` denial messages in the `/var/log/audit/audit.log` file. In this release, the `ceph-volume` utility sets the proper SELinux context (`ceph_var_lib_t`), on the OSD filesystem.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1609430 (view as bug list) | Environment: | ||
| Last Closed: | 2018-09-26 18:23:43 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: | 1584264, 1609430 | |||
|
Description
Boris Ranto
2018-07-27 22:30:17 UTC
Moving this bug to verified, there is no avc denial messages in /var/log/audit/audit.log Verified in ceph version 12.2.5-37.el7cp (7bac42c43d4cdcca7d0c4233344f9a3932636341) luminous (stable) 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-2018:2819 |